Hello Joe and everyone else,
I would like to thanks you for the article. Read this when it first came out and have since modified it for my need. Here are the modifications I made.
- Create table with contains Servers Name, Type (Prod or Development), Version number (2000 /2005) and Owner of the system (Finance, account, etc). This will all me to specify which systems I want to do remote execution on. So if I only want to run code against the development SQL 2000 servers only I can. Also, as new server come to our network I would just add it's info into this table and it done.
- Enhanced the error handling for server(s) that already have a link connection
- Made my server trusted by all the other servers so that passwords and ids are not needed for connection. My main server is completely locked down on all levels, don't need someone to connect and then have full access to the other servers.
- Made a generic version of the code so that I execute anything I need on the remote server. This works for my SSRS report page. I use this code to produce several reports which include:
1) Job failures report on all servers, production only and / or development onhly
2) SQL Error log analysis report
I can send you my updated code if you like.