I'm playing around a little bit with Rodney Landrum's [repository solution].
The solution works with dynamic connections to different data sources, e.g. the package loops through a table with a list of servers. Afterwards the package builds up a connection to each server and gathers some system relevant information. Now my little problem: How can I build up some kind of error handling if one of the listed servers is not available? By now the whole package will fail if more than 3 errors occur. So I'd like to check if the source is available. If not, log the non-reachable server in a separate table and go on with the remaining servers.
If you have any ideas how to achieve this please let me know.
Regards Dirk: http://www.sqlmag.com/article/sql-server-integration-services-ssis/use-ssrs-and-ssis-to-create-a-dba-repository
asked May 22, 2012 at 09:23 AM in Default
After a few hours working on other topics I got an idea on how to solve my problem. It's probably not the best way but it'll work for me: Before getting the actual data out of the different servers I will just use another loop container with a task to determine the servername and load it into a new table called "AvailableServers". This will be my recent "connect to" information. If the tasks fails, then I can write those faulty servers into a table called "NonAvailableServers".It's just a rough idea but I'll figure it out
answered May 22, 2012 at 01:19 PM