CODEWITHSUNDEEP
sql-serverssis
Rich
Rich

Reputation: 2279

When I save SSIS package the changes are lost

I have a SQL Server 2005 SSIS package with an Execute SQL task. I edit the SQL statement, go through the OKs to make the change. I go back in to the Execute SQL task- and the changes have taken hold. Great.

I now go to save the package. I click save. I look back in the Execute SQL task, and the changes have been lost.

What is going on here and how can I stop it?

Upvotes: 3

Views: 5998

Answers (3)

WFB
WFB

Reputation: 1

I found I was unable to change the "To" in the Send Mail Task. Or rather, I would press OK on the new value and then bring it up again and it would be the old value. What I did -- was to edit the dtsx file in Notepad by searching for the old value and changing it.

Upvotes: -2

Slava
Slava

Reputation: 41

I had the same issue. The reason was that I used a config file with all the executables included, and sql code is just a property of one of the executable which is stored in the config file. When you change your code the config file does NOT get updated, but when you close/open your project the values are getting pulled from the config file which reverse your change to the initial state!

In order to fix this you need either to exclude your executable from the config file (what I did) or re-create the config file every time you change the package.

I hope this helps.

Upvotes: 4

cairnz
cairnz

Reputation: 3957

  • Click the Execute SQL Task
  • Click F4 to see the list of properties
  • Click the Expressions line and then the little [...] box to see the expressions
  • Change the expressions (or remove them if you don't want your name/sqlstatementsource/etc. to be set dynamically).

This is a nice feature for reusability and template based development of SSIS packages. We use it allt he time.

Upvotes: 10

Related Questions