Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
fredong
Yak Posting Veteran
80 Posts |
Posted - 2009-12-30 : 00:57:07
|
Hi AllI have created each XML connection.dtsconfig file that located on my Test and and Prod servers residing on their local C:\. My purpose is to move the package from Test server to Prod server and call their local C:\ connection.dtsconfig file with the SQL statement I created on the Execute SQL task. However I do not see an option in the Execute SQL task I can set to call the XML connection.dtsconfig file. My goal it to have a dynamic connection on the Execute SQL task after moving the package from TEST to PROD envrionment. Any ideas? Thanks.k |
|
behrman
Yak Posting Veteran
76 Posts |
Posted - 2010-01-03 : 10:18:08
|
I want to know what exactly is your objective here and what is your execute sql task trying to do?As far as I can see you should be getting connection string properties (server/Dbname) from the config file and using those for your OLEDB conn manager which in turn should be used by your execute sql task.RAQ Report: Web-based Excel-like Java reporting tool |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2010-01-03 : 11:31:56
|
check this outhttp://blogs.egroup-us.com/?p=1455 |
|
|
fredong
Yak Posting Veteran
80 Posts |
Posted - 2010-01-03 : 11:39:31
|
First of all I had manually created the test dtsConfig file and it worked for all my script task. However, I added a Exexcute SQL task and went to OLEDB and choose new connection and I created a connection to my Test server enviroment. I want to know what happen if I move my package to my Production server enviroment will the Execute SQL Task calls the Production server connection since it it using the new connection? BTW I have another copy of test dtsConfig file located in the production server and connect to the production server for my Script task. Also I don't see an option in the Execute SQL Task OLEDB connection to choose the dtsConfig file. Perhaps you can show me the steps.Thanksk |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2010-01-03 : 11:55:52
|
The dtsConfig file is used to DEPLOY your package on another server. No, you're never too old to Yak'n'Roll if you're too young to die. |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
|
fredong
Yak Posting Veteran
80 Posts |
Posted - 2010-01-03 : 22:51:13
|
Hi Webfred,Perhaps I did not make myself clear. My package will delpoy to "TEST SISS server" but my Execute SQL Task in the package has a SQL statement is retrive the value from a "Test SQL data sever". Later once the QA Testing is passed I have to deploy the package to a PROD SSIS server and same thing the Execute SQL Task in the package will call the "PROD SQL data sever". I have manually created 2 XML dtsConfig files to connect "Test SQL data sever" and reside on the "TEST SISS server" and "Prod SISS server" physical server C:\. I am able to get the connection for my Script task to connect to XML dtsConfig file for the different environment but I am not able to get the connection for the Execute SQL Task to connection the diffirent environment dynamiacally. I do not see an option that the Execute SQL Task connection to choose the XML dtsConfig file. Perhaps I am missing something. Can you advise? Thanks.k |
|
|
|
|
|