Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Proper SSIS deployment method Expand / Collapse
Author
Message
Posted Tuesday, November 19, 2013 11:25 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Today @ 1:50 PM
Points: 56, Visits: 280
What is the proper way to deploy an ssis package?
More specifically, I find some level of complexity around what I thought were simple concepts.
In our situation, I developed some packages and sent them over to the operations team who tried to change the datasource to point to their test system. It just flat out won't work. Usually fails around the name of the datasource and the encryptsensitive flags.
Do I leave the credentials in the package? Do I set it to dontstoresensitive and let them pass the credentials in?
How do they change the datasources without it complaining that it wasn't in the developed package?

I think I don't understand the proper way to handle this.
The final product is going to be a deployed package to a server which I won't have much control over.
Post #1515698
Posted Tuesday, November 19, 2013 12:03 PM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Today @ 7:35 AM
Points: 547, Visits: 1,880
What version of BiDS/SSDT are you using?

Pre-2012, I believe all deployment was at the package level, and the accepted 'best practice' was to use DontSaveSensitive with configurations.

I am using 2012 and the project deployment model, which has some more options (deploying to a catalog with environments), in which case the server information can be a parameter, which gets mapped to environments when deploying. Still a bit annoying around encryption settings, though.
Post #1515717
Posted Tuesday, November 19, 2013 12:12 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Today @ 1:50 PM
Points: 56, Visits: 280
2008 R2.
I have been trying to get it to use dontsavesensitive and pass it creds. But my problem seems to be around the connectionmanager. If it deviates from the connections in the package, it seems to fail. That kind of kills the idea of deploying to lot's of servers.
Mine is slightly more complicated because these are executing against an Azure database. Azure treats each database as a new connection. Thus my requirement to be able to specify the connection at runtime. This is very frustrating.
Post #1515721
Posted Tuesday, November 19, 2013 1:37 PM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Today @ 7:35 AM
Points: 547, Visits: 1,880
Can't you use an expression for the connection string property?
Post #1515763
Posted Tuesday, November 19, 2013 2:16 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Today @ 1:50 PM
Points: 56, Visits: 280
I just made it much simpler. I stripped off all connections except the destination, and renamed it generically to 'destination' then instructed the ops to modify it in the ui. it works but it seems that the pw needs to be manually entered each time and it doesn't display. This works.
Post #1515777
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse