SQL Server Config issue
I have created a package . The source is DEVSQL\SQL1 with windows auth and the destination is TDEVSQL\SQL1 . I created a XML config file for source so i can change it for QA and DEV . I also created a config table in SQL server on DEV\QA\PROD so the package can dynamically get the destination details(TQASQL\SQL1) and TPRODSQL\SQL1. Somehow when i execute the package using Execute Package utility , the destination does not change from TDEVSQL\SQL1 to TQASQL\SQl1 if i pass the config file that connects to QASQL\SQL1. It still loads the data in TDEVSQL\SQL1 . We will copy the dts files manually to deploy it on QA\PROD and do not use main manifest to deploy. Is it a bug in SSIS or is there any solution to it ? Satish
April 12th, 2011 7:56pm

It is getting connected to QA server If I pass QA configuration file but not taking destination connection from QA SQL Server Config table but using it from DEV as defined the package during development Satish The boldified is the issue because somehow you overlooked how you manage your table connection or it merely could be just a typo somewhere, go inspect the part where you connect to the config db. SSIS 2008 quietly re-applies the dev config settings if you messed up with the config.Arthur My Blog
Free Windows Admin Tool Kit Click here and download it now
April 13th, 2011 3:08pm

XML config connects correctly. Don't you think if it is wrong , it will fail ? Satish
April 13th, 2011 3:20pm

Can you check the log created by the package? Any information / error/warning ?Regards and good Wishes, Deepak.
Free Windows Admin Tool Kit Click here and download it now
April 13th, 2011 3:24pm

OK, just to get things clear: * you configure the source with an XML config file (and what source I guess you mean the source that contains the data) * you configure the destination with a SQL Configuration table Why are you using two different types of package configurations mixed together? I asked you how you configure the connection to the SQL Server Configuration table. You said you use an XML config file for that purpose. So are there two XML config files, one for the source and one for configuring the connection to the SQL Config table? When the connection to the destination doesn't change when changing the package from environments, this means that something went wrong and that the default is used, aka the values set during design time. So what went wrong? The connection to the SQL Server Config table is not set correctly, it is overwritten by another configuration or the values in the config table are incorrect...MCTS, MCITP - Please mark posts as answered where appropriate.
April 13th, 2011 3:26pm

@Koen Why are you using two different types of package configurations mixed together? As we want to store the second connection and many other in SQL server config table. There are tera data connections that we want to use if this thing works I asked you how you configure the connection to the SQL Server Configuration table. You said you use an XML config file for that purpose. So are there two XML config files, one for the source and one for configuring the connection to the SQL Config table? I have one XML Config file and one SQL Server config Two connection conn1 from XML config file conn2 from SQL server Config table I rechecked everything including values. Satish
Free Windows Admin Tool Kit Click here and download it now
April 13th, 2011 4:20pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics