We have an SSIS package that is totally hosed (got corrupted somehow) so I’m trying to rebuild it from scratch. This package was built several years ago by a vendor that we no longer have ties to. As we started looking into it, we found a lot of strange things and I’m wondering if any of you have seen this sort of thing before.
1) Native SQL OLE DB / ADO Connection managers have expressions attached to them on the ConnectionString that is the same exact information as the CM would contain if it didn’t have an expression attached. For instance, a regular connection string in the properties might be “Data Source=MyServerDev;Initial Catalog=MyDB;Provider=SQLNCLI11.1;Integrated Security=SSPI;Auto Translate=False;”. And then when I scroll down to Expressions, there’s an expression attached to the ConnectionString property that is that exact same information verbatim.
2) Variables have expressions referencing themselves.
Has anyone ever seen coding like this before?
There are a lot of Script Component transformations in a group of Data Flow tasks (Given their position at the end of the precedence flow, I think they’re Destination instead of Source or Transformation types). I’m not sure if that has anything to do with it. But I’m really weirded out by this. It seems to be a lot of ridiculous redundancy to my eyes.
Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.