SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Proper SSIS deployment method


Proper SSIS deployment method

Author
Message
mortalic
mortalic
SSC-Enthusiastic
SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)

Group: General Forum Members
Points: 132 Visits: 390
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.
Nevyn
Nevyn
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1590 Visits: 3149
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.
mortalic
mortalic
SSC-Enthusiastic
SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)

Group: General Forum Members
Points: 132 Visits: 390
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.
Nevyn
Nevyn
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1590 Visits: 3149
Can't you use an expression for the connection string property?
mortalic
mortalic
SSC-Enthusiastic
SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)

Group: General Forum Members
Points: 132 Visits: 390
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.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search