Hi All,
I am new to SSIS aspect of SQL server.I am using SQL server 2005 BIDS.I have developed one data flow task which fetch data from one table(SQl Server A) and insert it to another table(SQL Server B).In my development environment it worked properly.So i decided to decided to deploy it to production servers.Obviously production servers are different from development environment.
Details of package :-
- Package Config Type :- SQl server (This table stored connection strings for Source and Destination table)
- Package Config Table Name : -SSIS_Configurations
In development environment Data flow task fetched Connection strings from SSIS_Configurationstable.
When I run deployment utility i.e. '.SSISDeploymentManifest' file it guided me and I successfully installed package on production servers.After deployment checked configuration table 'SSIS_Configurations' on target server ,it was not present there.Without this table my package would be useless.
When I tried to execute package manually (Rt click on package-->Run Package) it populated new screen called Exceute Package Utility. When I checked Connection Managers ,it was showing Development Server's Connections string (OLE DB Connection string which I set during creation of task in development environment).
So I have couple of questions
- why my table SSIS_Configurations was not created during deployment of package using '.SSISDeploymentManifest' file.
- Why,even after deployment in production environment ,my connection manager was showing Development DB server connection strings.
Guys your input would be very helpful to me.Thanks in advance.
Banky