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 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
>

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
>

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
>