DBA's often monitor Backups, Replication e.t.c manually or through some automation but there is one thing which needs to be monitored is linked server. Often there may be some issue in linked server and DBA's will not know till Application user raises issue. Also there is a straight method (sp_TestLinkedServer) to test linked servers in SQL 2005 will say pass even the Access is deleted from the path. So this script will help you to monitor Linked servers from SQL 2000 and i have posted another SQL 2005 version of this script.
Also fine below the test i have done on this script and options available to test linked servers.
Below are the tests done and their status.
The RED issues cannot be captured in SQL 2000 (No option to TRY/CATCH ???) and thus why it is good to monitor linked servers from SQL 2005.
Below are the options available to test linked server
In the above we cannot use sp_tableex since incase SQL server is not running or access denied etc then runtime error will come so only we are using sp_OA.
Any enhancements/suggestions are always welcome!