November 15, 2012 by Kenneth Fisher
Over the last couple of weeks I’ve set up a SSIS package that will loop through a group of servers and export the list of databases to a central location. I used a Foreach Item Enumerator to list the servers but honestly those require a bit too much maintenance for me. In my office we have 60-70 instances right now and are merging with a group with 60+ more. In my mind that’s a headache waiting to happen. So today I’m going to modify the package to pull and loop through a list of servers from a table. Still somewhat manual (entering records into the table) but at least I don’t have to open the package each time.
- Starting from Step 2.
- First let’s do something I should have done from the beginning. Rename all of the objects to something meaningful.
- Create a table in the DataStore instance to hold the list of instances.
CREATE TABLE InstanceList ( InstanceName varchar(255) NOT NULL CONSTRAINT pk_InstanceList PRIMARY KEY, GetDatabaseList bit NOT NULL, Active bit NOT NULL )
- Add rows to your table pointing to the servers you are interested in. Make sure that GetDatabaseList and Active are both set to 1.
- Create a new variable in the package called “ServerList” of type Object
- Add a new Execute SQL task to pull the list of instances from our new table.
- Under the General tab
- On the Result Set
- tab Click the Add button
- Change the Result Name to 0
- Change the Variable Name to User::ServerList.
- Attach the task to the previous one.
- In the ForEach loop properties under the Collection tab
- Change the Enumerator to a “ForEach ADO Enumerator”
- Change the variable to “User::ServerList”
- Leave Enumeration Mode “Rows in the first table”
At this point we now have a package that will loop through a control table containing a list of instances. Then for each instance it pulls a list of databases and stores it into a central location. Hopefully I’ve managed to make these posts clear enough that everyone can follow and easily duplicate what I’ve done. If not then please feel free to comment and I’ll do my best to help you get up and running.
Note: Unfortunately the package file got corrupted somehow and I had to get rid of it. I’ll try to re-create it (and may even re-do this series) and get it reposted one of these days. Of course this was using the SQL 2005 version of SSIS which is no longer really up to date.