June 8, 2011 at 8:43 am
We just migrated a database from one server to another, including its DTS packages. When we transfered the dts packages, I went into Disconnected Edit and changed all references from SQLPRD2 to SQLPRD6 (our server names). I checked all variables, all scripts, etc. Yet when the package runs, I see records still being added to the database in the old server SQLPRD2. I thought Disconnected Edit is where you see everything about a DTS package. Is there something we missed?
June 8, 2011 at 5:18 pm
Are the connections contained in global variables that are set at run time? If so, have you checked the DTSRUN command for values following /A?
Greg
June 9, 2011 at 6:01 pm
Problem solved.
The DTS components that were installed were behaving strangely. Everytime I opened a package an error kept popping up. I don't remember what the message was off hand. But I noticed that this was constantly happening. At the beginning I kept ignoring the error because after I clicked OK it opened the package and I continued.
Now I'm starting to see why this error kept popping. For some reason the DTS component wasn't able to read the connection tasks. So when I bypassed it, I never realized that the connection property's subnode was missing on the left pane of Disconnected Edit. So I kept setting the DataSource on the right pane. Little did I know that it appeared to be saving my new value but it wasn't.
When the DBA called me, he opened the package on his computer. His connection property's subnode was showing up with a little plus sign on the left pane. When he clicked the plus sign on the left pane, he clicked on the DataSource property and lo-and behold, my old value was still there, even though the new value was showing up in the DataSource property on the right pane.
Hopefully, this might help someone in the future.
Ray Cacciatore
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply