• tim.ffitch 25252 - Monday, February 26, 2018 9:35 AM

    The connection string expression may make sense if package reads from a parameter file to get the connection string and they have set a design default.
    Variables referencing themselves is a No No! It will create a circular reference and send the package into a spin.
    What version of SQL was the package originally designed in and how was it deployed? With project deployment for example used in SQL 2012 onward you can recover a lost project or package by recovering it from the SSISDB catalog.

    It was designed in SQL 2008. We've since upgraded to SQL 2012. It was deployed straight to IS via the GUI with the Import Package right-click option, but we have a history of the package in TFS.

    The odd thing is, until recently the package worked fine.

    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.