CHEKING SQL AGENT IN A LAN

Hi we have a LAN of 400 stations and sometimes the agent stop in several
machines, causing jobs not to run, so i have to check manually if the agent
is running. The question is: There's a fast way to check if all the agents in
my network are started?
* my version is sql server2000 with SP4
Thanks
Have a look at "Mutiserver Adminstration" in BOL.
"amejiae" wrote:

> Hi we have a LAN of 400 stations and sometimes the agent stop in several
> machines, causing jobs not to run, so i have to check manually if the agent
> is running. The question is: There's a fast way to check if all the agents in
> my network are started?
> * my version is sql server2000 with SP4
> Thanks
|||You might benefit greatly from a product available at:
http://www.sqlsentry.net/
Andrew J. Kelly SQL MVP
"amejiae" <amejiae@.discussions.microsoft.com> wrote in message
news:3B73EBF5-D28D-4DCA-9672-35BD27BA26B9@.microsoft.com...
> Hi we have a LAN of 400 stations and sometimes the agent stop in several
> machines, causing jobs not to run, so i have to check manually if the
> agent
> is running. The question is: There's a fast way to check if all the agents
> in
> my network are started?
> * my version is sql server2000 with SP4
> Thanks
|||you could write a script swith SQLDMO
"amejiae" <amejiae@.discussions.microsoft.com> wrote in message
news:3B73EBF5-D28D-4DCA-9672-35BD27BA26B9@.microsoft.com...
> Hi we have a LAN of 400 stations and sometimes the agent stop in several
> machines, causing jobs not to run, so i have to check manually if the
> agent
> is running. The question is: There's a fast way to check if all the agents
> in
> my network are started?
> * my version is sql server2000 with SP4
> Thanks
|||Or you can take a look at IDERA's Diagnostic Manager.
"amejiae" wrote:

> Hi we have a LAN of 400 stations and sometimes the agent stop in several
> machines, causing jobs not to run, so i have to check manually if the agent
> is running. The question is: There's a fast way to check if all the agents in
> my network are started?
> * my version is sql server2000 with SP4
> Thanks

CHEKING SQL AGENT IN A LAN

Hi we have a LAN of 400 stations and sometimes the agent stop in several
machines, causing jobs not to run, so i have to check manually if the agent
is running. The question is: There's a fast way to check if all the agents i
n
my network are started?
* my version is sql server2000 with SP4
ThanksHave a look at "Mutiserver Adminstration" in BOL.
"amejiae" wrote:

> Hi we have a LAN of 400 stations and sometimes the agent stop in several
> machines, causing jobs not to run, so i have to check manually if the agen
t
> is running. The question is: There's a fast way to check if all the agents
in
> my network are started?
> * my version is sql server2000 with SP4
> Thanks|||You might benefit greatly from a product available at:
http://www.sqlsentry.net/
Andrew J. Kelly SQL MVP
"amejiae" <amejiae@.discussions.microsoft.com> wrote in message
news:3B73EBF5-D28D-4DCA-9672-35BD27BA26B9@.microsoft.com...
> Hi we have a LAN of 400 stations and sometimes the agent stop in several
> machines, causing jobs not to run, so i have to check manually if the
> agent
> is running. The question is: There's a fast way to check if all the agents
> in
> my network are started?
> * my version is sql server2000 with SP4
> Thanks|||you could write a script swith SQLDMO
"amejiae" <amejiae@.discussions.microsoft.com> wrote in message
news:3B73EBF5-D28D-4DCA-9672-35BD27BA26B9@.microsoft.com...
> Hi we have a LAN of 400 stations and sometimes the agent stop in several
> machines, causing jobs not to run, so i have to check manually if the
> agent
> is running. The question is: There's a fast way to check if all the agents
> in
> my network are started?
> * my version is sql server2000 with SP4
> Thanks|||Or you can take a look at IDERA's Diagnostic Manager.
"amejiae" wrote:

> Hi we have a LAN of 400 stations and sometimes the agent stop in several
> machines, causing jobs not to run, so i have to check manually if the agen
t
> is running. The question is: There's a fast way to check if all the agents
in
> my network are started?
> * my version is sql server2000 with SP4
> Thanks

CHEKING SQL AGENT IN A LAN

Hi we have a LAN of 400 stations and sometimes the agent stop in several
machines, causing jobs not to run, so i have to check manually if the agent
is running. The question is: There's a fast way to check if all the agents in
my network are started?
* my version is sql server2000 with SP4
ThanksHave a look at "Mutiserver Adminstration" in BOL.
"amejiae" wrote:
> Hi we have a LAN of 400 stations and sometimes the agent stop in several
> machines, causing jobs not to run, so i have to check manually if the agent
> is running. The question is: There's a fast way to check if all the agents in
> my network are started?
> * my version is sql server2000 with SP4
> Thanks|||You might benefit greatly from a product available at:
http://www.sqlsentry.net/
Andrew J. Kelly SQL MVP
"amejiae" <amejiae@.discussions.microsoft.com> wrote in message
news:3B73EBF5-D28D-4DCA-9672-35BD27BA26B9@.microsoft.com...
> Hi we have a LAN of 400 stations and sometimes the agent stop in several
> machines, causing jobs not to run, so i have to check manually if the
> agent
> is running. The question is: There's a fast way to check if all the agents
> in
> my network are started?
> * my version is sql server2000 with SP4
> Thanks|||you could write a script swith SQLDMO
"amejiae" <amejiae@.discussions.microsoft.com> wrote in message
news:3B73EBF5-D28D-4DCA-9672-35BD27BA26B9@.microsoft.com...
> Hi we have a LAN of 400 stations and sometimes the agent stop in several
> machines, causing jobs not to run, so i have to check manually if the
> agent
> is running. The question is: There's a fast way to check if all the agents
> in
> my network are started?
> * my version is sql server2000 with SP4
> Thanks|||Or you can take a look at IDERA's Diagnostic Manager.
"amejiae" wrote:
> Hi we have a LAN of 400 stations and sometimes the agent stop in several
> machines, causing jobs not to run, so i have to check manually if the agent
> is running. The question is: There's a fast way to check if all the agents in
> my network are started?
> * my version is sql server2000 with SP4
> Thanks

checksum_agg and row size error. Require explanation.

Hi,

I can see that by using the object ID rather that the object name, the
following SQL query works. Has anybody got any idea what is causing the
error?

-- Works OK
select o.id
,checksum_agg(binary_checksum(m.text))
from sysobjects o
,syscomments m
where o.id = m.id
and o.xtype in ('FN','IF','P','TF','TR','V')
group by o.id

-- Error
-- Server: Msg 1540, Level 16, State 1, Line 1
-- Cannot sort a row of size 8096, which is greater than the
-- allowable maximum of 8094.
select object_name(o.id)
,checksum_agg(binary_checksum(m.text))
from sysobjects o
,syscomments m
where o.id = m.id
and o.xtype in ('FN','IF','P','TF','TR','V')
group by object_name(o.id)

-- Error
-- Server: Msg 1540, Level 16, State 1, Line 1
-- Cannot sort a row of size 8096, which is greater than the
-- allowable maximum of 8094.
select o.name
,checksum_agg(binary_checksum(m.text))
from sysobjects o
,syscomments m
where o.id = m.id
and o.xtype in ('FN','IF','P','TF','TR','V')
group by o.name

-- Workaround
select getdate()
,object_name(x.id)
,check_sum
from (select m.id
,checksum_agg(binary_checksum(m.text)) as check_sum
from syscomments m
inner join
sysobjects o
on m.id = o.id
where o.xtype in ('FN','IF','P','TF','TR','V')
group by m.id) as x

Regards

LiamUse "OPTION (ROBUST PLAN)":

select o.name
,checksum_agg(binary_checksum(*m.text))
from sysobjects o
,syscomments m
where o.id = m.id
and o.xtype in ('FN','IF','P','TF','TR','V')
group by o.name
OPTION (ROBUST PLAN)

This forces SQL Server to use a plan that works for the maximum
potential row size.

Razvan

CheckPoint causing long SP durations

There are thousands of continuous SELECTS on the tables per min and durations
are good and low.
Periodically, there are massive INSERTS done in batch that number in the
many thousands.
While monitoring the Checkpoint Pages/Sec counter, whenever the checkpoint
is issued by SQL, the Duration times (which are monitored in Profiler) go up
dramatically causing client issues and then the duration times go back down
to low after the checkpoint has flushed the dirty pages to disk.
Any suggestions? IO to disk?
Don
SQL 2000 SP4
A checkpoint flushes all the dirty pages of the current database to disk.
When you have a lot of modified pages (as in your case when you do massive
inserts via a batch job), it can put considerable strain on the I/O subsystem.
If checkpoints are a serious problem for you, upgrading to a better your I/O
subsystem will always help :-) You can also consider pacing your INSERTs if
you can afford lengthening your batch processing time.
Note that there is a reason why people usually schedule their batch jobs
during a relatively less busy time period.
Linchi
"donsql22222" wrote:

> There are thousands of continuous SELECTS on the tables per min and durations
> are good and low.
> Periodically, there are massive INSERTS done in batch that number in the
> many thousands.
> While monitoring the Checkpoint Pages/Sec counter, whenever the checkpoint
> is issued by SQL, the Duration times (which are monitored in Profiler) go up
> dramatically causing client issues and then the duration times go back down
> to low after the checkpoint has flushed the dirty pages to disk.
> Any suggestions? IO to disk?
> Don
> SQL 2000 SP4
>
|||In addition to what Linchi says (which should be heeded by the way) make
sure your log files are not on the same physical drive array as the data or
tempdb.
Andrew J. Kelly SQL MVP
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:2BD564B3-C3A7-46D5-8F39-F6F4935CA69D@.microsoft.com...[vbcol=seagreen]
>A checkpoint flushes all the dirty pages of the current database to disk.
> When you have a lot of modified pages (as in your case when you do massive
> inserts via a batch job), it can put considerable strain on the I/O
> subsystem.
> If checkpoints are a serious problem for you, upgrading to a better your
> I/O
> subsystem will always help :-) You can also consider pacing your INSERTs
> if
> you can afford lengthening your batch processing time.
> Note that there is a reason why people usually schedule their batch jobs
> during a relatively less busy time period.
> Linchi
> "donsql22222" wrote: