I've developed and am deploying a very important enterprise wide app for a
client. This app controls virtually everything the client does, and has
been thoroughly tested. However, I am a bit concerned about sql server
2000.
I noticed just the other day - still testing - that the server, when opened
in EM, said 'suspect'. I had been doing some fooling around and I know what
caused it. But my concern is, how can I monitor the server for this or
other failures to be able to react quickly - with a backup when necessary -
whenever something serious occurs? Is there a way, either inside vb .net or
by other means of continually polling the server for its health?
Thanks for any recommendations.
Regards,
Bernie Yaeger
Start a service application to continously run SELECT
DATABASEPROPERTYEX('pubs', 'Status') and check it's results?
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
news:WaqAc.39196$0b.10585827@.news4.srv.hcvlny.cv.n et...
> I've developed and am deploying a very important enterprise wide app for a
> client. This app controls virtually everything the client does, and has
> been thoroughly tested. However, I am a bit concerned about sql server
> 2000.
> I noticed just the other day - still testing - that the server, when
opened
> in EM, said 'suspect'. I had been doing some fooling around and I know
what
> caused it. But my concern is, how can I monitor the server for this or
> other failures to be able to react quickly - with a backup when
necessary -
> whenever something serious occurs? Is there a way, either inside vb .net
or
> by other means of continually polling the server for its health?
> Thanks for any recommendations.
> Regards,
> Bernie Yaeger
>
Showing posts with label controls. Show all posts
Showing posts with label controls. Show all posts
Monday, March 19, 2012
monitoring sql server 2000 for problems
I've developed and am deploying a very important enterprise wide app for a
client. This app controls virtually everything the client does, and has
been thoroughly tested. However, I am a bit concerned about sql server
2000.
I noticed just the other day - still testing - that the server, when opened
in EM, said 'suspect'. I had been doing some fooling around and I know what
caused it. But my concern is, how can I monitor the server for this or
other failures to be able to react quickly - with a backup when necessary -
whenever something serious occurs? Is there a way, either inside vb .net or
by other means of continually polling the server for its health?
Thanks for any recommendations.
Regards,
Bernie YaegerStart a service application to continously run SELECT
DATABASEPROPERTYEX('pubs', 'Status') and check it's results?
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
news:WaqAc.39196$0b.10585827@.news4.srv.hcvlny.cv.net...
> I've developed and am deploying a very important enterprise wide app for a
> client. This app controls virtually everything the client does, and has
> been thoroughly tested. However, I am a bit concerned about sql server
> 2000.
> I noticed just the other day - still testing - that the server, when
opened
> in EM, said 'suspect'. I had been doing some fooling around and I know
what
> caused it. But my concern is, how can I monitor the server for this or
> other failures to be able to react quickly - with a backup when
necessary -
> whenever something serious occurs? Is there a way, either inside vb .net
or
> by other means of continually polling the server for its health?
> Thanks for any recommendations.
> Regards,
> Bernie Yaeger
>
client. This app controls virtually everything the client does, and has
been thoroughly tested. However, I am a bit concerned about sql server
2000.
I noticed just the other day - still testing - that the server, when opened
in EM, said 'suspect'. I had been doing some fooling around and I know what
caused it. But my concern is, how can I monitor the server for this or
other failures to be able to react quickly - with a backup when necessary -
whenever something serious occurs? Is there a way, either inside vb .net or
by other means of continually polling the server for its health?
Thanks for any recommendations.
Regards,
Bernie YaegerStart a service application to continously run SELECT
DATABASEPROPERTYEX('pubs', 'Status') and check it's results?
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
news:WaqAc.39196$0b.10585827@.news4.srv.hcvlny.cv.net...
> I've developed and am deploying a very important enterprise wide app for a
> client. This app controls virtually everything the client does, and has
> been thoroughly tested. However, I am a bit concerned about sql server
> 2000.
> I noticed just the other day - still testing - that the server, when
opened
> in EM, said 'suspect'. I had been doing some fooling around and I know
what
> caused it. But my concern is, how can I monitor the server for this or
> other failures to be able to react quickly - with a backup when
necessary -
> whenever something serious occurs? Is there a way, either inside vb .net
or
> by other means of continually polling the server for its health?
> Thanks for any recommendations.
> Regards,
> Bernie Yaeger
>
monitoring sql server 2000 for problems
I've developed and am deploying a very important enterprise wide app for a
client. This app controls virtually everything the client does, and has
been thoroughly tested. However, I am a bit concerned about sql server
2000.
I noticed just the other day - still testing - that the server, when opened
in EM, said 'suspect'. I had been doing some fooling around and I know what
caused it. But my concern is, how can I monitor the server for this or
other failures to be able to react quickly - with a backup when necessary -
whenever something serious occurs? Is there a way, either inside vb .net or
by other means of continually polling the server for its health?
Thanks for any recommendations.
Regards,
Bernie YaegerStart a service application to continously run SELECT
DATABASEPROPERTYEX('pubs', 'Status') and check it's results?
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
news:WaqAc.39196$0b.10585827@.news4.srv.hcvlny.cv.net...
> I've developed and am deploying a very important enterprise wide app for a
> client. This app controls virtually everything the client does, and has
> been thoroughly tested. However, I am a bit concerned about sql server
> 2000.
> I noticed just the other day - still testing - that the server, when
opened
> in EM, said 'suspect'. I had been doing some fooling around and I know
what
> caused it. But my concern is, how can I monitor the server for this or
> other failures to be able to react quickly - with a backup when
necessary -
> whenever something serious occurs? Is there a way, either inside vb .net
or
> by other means of continually polling the server for its health?
> Thanks for any recommendations.
> Regards,
> Bernie Yaeger
>
client. This app controls virtually everything the client does, and has
been thoroughly tested. However, I am a bit concerned about sql server
2000.
I noticed just the other day - still testing - that the server, when opened
in EM, said 'suspect'. I had been doing some fooling around and I know what
caused it. But my concern is, how can I monitor the server for this or
other failures to be able to react quickly - with a backup when necessary -
whenever something serious occurs? Is there a way, either inside vb .net or
by other means of continually polling the server for its health?
Thanks for any recommendations.
Regards,
Bernie YaegerStart a service application to continously run SELECT
DATABASEPROPERTYEX('pubs', 'Status') and check it's results?
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
news:WaqAc.39196$0b.10585827@.news4.srv.hcvlny.cv.net...
> I've developed and am deploying a very important enterprise wide app for a
> client. This app controls virtually everything the client does, and has
> been thoroughly tested. However, I am a bit concerned about sql server
> 2000.
> I noticed just the other day - still testing - that the server, when
opened
> in EM, said 'suspect'. I had been doing some fooling around and I know
what
> caused it. But my concern is, how can I monitor the server for this or
> other failures to be able to react quickly - with a backup when
necessary -
> whenever something serious occurs? Is there a way, either inside vb .net
or
> by other means of continually polling the server for its health?
> Thanks for any recommendations.
> Regards,
> Bernie Yaeger
>
Wednesday, March 7, 2012
Monitor SQL agent
Hi,
we know that SQL agent controls the job's schedule & running, but if SQL
agent stop working, all jobs will not be able to be executed, is there any
tool/method to monitor SQL agent if it stopped, hung or wrong from another
SQL server, so the other SQL server will send operator notification?
Thanks in advance.
JackNot directly. But you can code it yourself. Use a combination of xp_cmdshell and netsvc (I believe
that the utility is called with which you can check and start/stop services on another machine). You
can pull the result into a table and then check against that table.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jack" <chongh.hc@.gmail.com> wrote in message news:eHqYn73PFHA.3076@.tk2msftngp13.phx.gbl...
> Hi,
> we know that SQL agent controls the job's schedule & running, but if SQL agent stop working, all
> jobs will not be able to be executed, is there any tool/method to monitor SQL agent if it stopped,
> hung or wrong from another SQL server, so the other SQL server will send operator notification?
> Thanks in advance.
> Jack
>
we know that SQL agent controls the job's schedule & running, but if SQL
agent stop working, all jobs will not be able to be executed, is there any
tool/method to monitor SQL agent if it stopped, hung or wrong from another
SQL server, so the other SQL server will send operator notification?
Thanks in advance.
JackNot directly. But you can code it yourself. Use a combination of xp_cmdshell and netsvc (I believe
that the utility is called with which you can check and start/stop services on another machine). You
can pull the result into a table and then check against that table.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jack" <chongh.hc@.gmail.com> wrote in message news:eHqYn73PFHA.3076@.tk2msftngp13.phx.gbl...
> Hi,
> we know that SQL agent controls the job's schedule & running, but if SQL agent stop working, all
> jobs will not be able to be executed, is there any tool/method to monitor SQL agent if it stopped,
> hung or wrong from another SQL server, so the other SQL server will send operator notification?
> Thanks in advance.
> Jack
>
Monitor SQL agent
Hi,
we know that SQL agent controls the job's schedule & running, but if SQL
agent stop working, all jobs will not be able to be executed, is there any
tool/method to monitor SQL agent if it stopped, hung or wrong from another
SQL server, so the other SQL server will send operator notification?
Thanks in advance.
JackNot directly. But you can code it yourself. Use a combination of xp_cmdshell
and netsvc (I believe
that the utility is called with which you can check and start/stop services
on another machine). You
can pull the result into a table and then check against that table.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jack" <chongh.hc@.gmail.com> wrote in message news:eHqYn73PFHA.3076@.tk2msftngp13.phx.gbl...[
vbcol=seagreen]
> Hi,
> we know that SQL agent controls the job's schedule & running, but if SQL a
gent stop working, all
> jobs will not be able to be executed, is there any tool/method to monitor
SQL agent if it stopped,
> hung or wrong from another SQL server, so the other SQL server will send o
perator notification?
> Thanks in advance.
> Jack
>[/vbcol]
we know that SQL agent controls the job's schedule & running, but if SQL
agent stop working, all jobs will not be able to be executed, is there any
tool/method to monitor SQL agent if it stopped, hung or wrong from another
SQL server, so the other SQL server will send operator notification?
Thanks in advance.
JackNot directly. But you can code it yourself. Use a combination of xp_cmdshell
and netsvc (I believe
that the utility is called with which you can check and start/stop services
on another machine). You
can pull the result into a table and then check against that table.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jack" <chongh.hc@.gmail.com> wrote in message news:eHqYn73PFHA.3076@.tk2msftngp13.phx.gbl...[
vbcol=seagreen]
> Hi,
> we know that SQL agent controls the job's schedule & running, but if SQL a
gent stop working, all
> jobs will not be able to be executed, is there any tool/method to monitor
SQL agent if it stopped,
> hung or wrong from another SQL server, so the other SQL server will send o
perator notification?
> Thanks in advance.
> Jack
>[/vbcol]
Monitor SQL agent
Hi,
we know that SQL agent controls the job's schedule & running, but if SQL
agent stop working, all jobs will not be able to be executed, is there any
tool/method to monitor SQL agent if it stopped, hung or wrong from another
SQL server, so the other SQL server will send operator notification?
Thanks in advance.
Jack
Not directly. But you can code it yourself. Use a combination of xp_cmdshell and netsvc (I believe
that the utility is called with which you can check and start/stop services on another machine). You
can pull the result into a table and then check against that table.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jack" <chongh.hc@.gmail.com> wrote in message news:eHqYn73PFHA.3076@.tk2msftngp13.phx.gbl...
> Hi,
> we know that SQL agent controls the job's schedule & running, but if SQL agent stop working, all
> jobs will not be able to be executed, is there any tool/method to monitor SQL agent if it stopped,
> hung or wrong from another SQL server, so the other SQL server will send operator notification?
> Thanks in advance.
> Jack
>
we know that SQL agent controls the job's schedule & running, but if SQL
agent stop working, all jobs will not be able to be executed, is there any
tool/method to monitor SQL agent if it stopped, hung or wrong from another
SQL server, so the other SQL server will send operator notification?
Thanks in advance.
Jack
Not directly. But you can code it yourself. Use a combination of xp_cmdshell and netsvc (I believe
that the utility is called with which you can check and start/stop services on another machine). You
can pull the result into a table and then check against that table.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jack" <chongh.hc@.gmail.com> wrote in message news:eHqYn73PFHA.3076@.tk2msftngp13.phx.gbl...
> Hi,
> we know that SQL agent controls the job's schedule & running, but if SQL agent stop working, all
> jobs will not be able to be executed, is there any tool/method to monitor SQL agent if it stopped,
> hung or wrong from another SQL server, so the other SQL server will send operator notification?
> Thanks in advance.
> Jack
>
Subscribe to:
Posts (Atom)