2005 Connection Portability

[jasonp45]

I am migrating to SQL Server 2005 and have successfully parsed and transformed some flat-files and loaded them into SQL Server tables.

I get files from multiple sources, and each source tends to stay in a consistent format.

Lets say I've created a dtsx package to transform and load one flat-file...what is the easiest way to transform and load subsequent files that are in identical format? Basically the only thing changing is the source flat-file's name and the target SQL table's name.

It's important for my archival purposes that I keep a persistent, distinct package for each file, so I don't want to open up my previous package and modify it, although I could certainly do that and do a 'save as'. Optimally I'd like to not have to open VisualStudio at all but just tweak the xml if all I need to do is change a couple of paths.

But I believe there must be a more elegant way that I'm ignorant of, perhaps via package configuration or variables.

Any help appreciated!

 

[mrdenny]

You can use a Script object to change the connection information on the package to load the data.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com