kenn3th.w0ng (8/25/2014)
The idea is not to test the contents of the table, but the ability to execute anything on a particular schema or database. The fact that you could tells me that it passes the litmus test that the server is online.There's also a problem with the need to centrally manage the code and the configuration. I know there's something for registered servers in SSMS, but we're doing this in the context that it's a cheap non-NetCool solution to monitoring outage.
Then why do a SELECT COUNT(*) FROM someschema.sometable? Like I said, a simple SELECT @@SERVERNAME works.
As Mark said as well, there are tools out there as well. Some are free, why not use them? If it has to be something developed in house, I still think PowerShell is a very good tool for this particular application.