<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
Article Discussions
»
Article Discussions by Author
»
Discuss Content Posted by Zach Mattson
»
SSIS for Multiple Environments
20 posts, Page 2 of 2
««
1
2
SSIS for Multiple Environments
Rate Topic
Display Mode
Topic Options
Author
Message
ryan.lawrence
ryan.lawrence
Posted Tuesday, April 27, 2010 9:30 AM
SSC Veteran
Group: General Forum Members
Last Login: Wednesday, October 03, 2012 10:08 AM
Points: 214,
Visits: 81
we use dtexec, which when run in the context of a scheduler will respond to a kill statement.
if we kill the job in the scheduler it will kill the ssis package at the point it was processing in about 3 - 4 seconds.
Post #911234
Jorge Novo-@ETLDEVDBA
Jorge Novo-@ETLDEVDBA
Posted Tuesday, April 27, 2010 9:46 AM
SSC-Enthusiastic
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 8:55 AM
Points: 137,
Visits: 250
Why storing the ssis at the File system level instead of the server? Storing packages at the file system is a security problem. A better way will be to store the package in the server also, store all metadata relate information in a table, this will provided a better more stable package to maintain.
Post #911249
djenkins
djenkins
Posted Tuesday, April 27, 2010 10:01 AM
Forum Newbie
Group: General Forum Members
Last Login: Wednesday, April 28, 2010 10:59 PM
Points: 2,
Visits: 11
Actually I reviewed by NT script and I do use DTEXEC instead of DTSRUN (I must had DTS packages on my mind!).
Another great thing about using a NT Batch script is that you can evaluate the ERRORLEVEL code from the DTEXEC command. This is a great way to properly know if you package did succeed or not. This also allows you to properly pass the Exit code to your job scheduler (ie: IBM Tivoli Job Scheduler) to know if the job was successful.
You can findout all about the DTEXEC command in BOL.
Post #911269
danv
danv
Posted Tuesday, April 27, 2010 11:19 AM
SSC-Enthusiastic
Group: General Forum Members
Last Login: Tuesday, April 16, 2013 12:33 PM
Points: 163,
Visits: 121
<ryan>
Interesting, that's how we'd like to ours to behave.
We use SQL Agent as our job scheduler. Stopping the job step leaves a thread of dtexec running the package and it won't stop until killed by pid. What job scheduler do you use?
</ryan>
As for storing packages in the filesystem: 1) it eases our deployments 2) you can't use relative paths in MSDB. Security needs to be taken care of with folder permissions etc. One disadvantage to this is also that we're not having the packages backed up as part of the msdb backups, but rely on our storage backups in the data center - which we are ok with.
Post #911312
ryan.lawrence
ryan.lawrence
Posted Tuesday, April 27, 2010 11:56 AM
SSC Veteran
Group: General Forum Members
Last Login: Wednesday, October 03, 2012 10:08 AM
Points: 214,
Visits: 81
zarathustra >>> we use CA Autosys
Post #911341
Robbob
Robbob
Posted Wednesday, April 28, 2010 10:02 AM
Grasshopper
Group: General Forum Members
Last Login: Tuesday, July 03, 2012 6:26 AM
Points: 12,
Visits: 204
Hi this is a great article. I am very familar with SSIS and would like any information on where I can get some more specifics on Multi Environment implementation. I have not had the need to create a Proxy or a credential account as you mention in your article. so I am trying to follow along and I think I have the jist of it. One question I have is when developing the package on your local machine and then running tests in each environment do you set package security up to a specific account? We have had some issues here with the credentials being saved as part of the package so we just use Passwords but I would like to know more about the credential implementation. Any info anyone can give on this topic is greatly appreciated.
Thanks,
Rob
Post #912149
WI-DBA
WI-DBA
Posted Wednesday, April 28, 2010 10:15 AM
SSC Journeyman
Group: General Forum Members
Last Login: Friday, May 17, 2013 9:36 AM
Points: 93,
Visits: 545
When a developer runs the package from their machine, it will (in our case) connect as dbo to the Configuration View - the reason being the SSIS developers our part of a group that has higher privs on DEV. If you use sql logins, there will be a bit more management involved when doing the promotes from the developer, to the qa system, etc. When we move the package to a Test environment, the credential/proxy take care of the security. The package execution takes on its (job step owners) credentials.
If I missed the question, please re-phrase and I will give it another shot.
Cheers
http://twitter.com/widba
http://widba.blogspot.com/
Post #912168
Toby White
Toby White
Posted Wednesday, April 28, 2010 10:17 AM
SSC-Addicted
Group: General Forum Members
Last Login: Friday, November 09, 2012 2:48 PM
Points: 493,
Visits: 636
One question I have is when developing the package on your local machine and then running tests in each environment do you set package security up to a specific account?
The way I handle this is by using the SQL Agent account or proxy. The package doesn't have any different security persay, but the security of the different agent/proxy accounts varries. Infact I developed a way to have one SSIS_configurations table for several environments.
SSIS_configurations can be a view/function that returns the data depending on what account (suser_sname()) calls it.
Post #912170
SQLRNNR
SQLRNNR
Posted Wednesday, April 28, 2010 10:43 AM
SSCoach
Group: General Forum Members
Last Login: Yesterday @ 1:07 PM
Points: 18,733,
Visits: 12,332
Nice article and very useful information.
We use a table in each environment.
Jason
AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server 2008
SQL RNNR
Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #912190
danv
danv
Posted Wednesday, April 28, 2010 9:50 PM
SSC-Enthusiastic
Group: General Forum Members
Last Login: Tuesday, April 16, 2013 12:33 PM
Points: 163,
Visits: 121
ryan thanks alot for the info.
robert. are you referring to the package protection level?
when we are in development we EncryptSensitiveWithUserKey enabling each developer to do their own thing while working locally. when we put our packages to DEV or UAT or PROD environments we EncryptSensitiveWithPassword with a strong common password.
this might have some useful info: http://msdn.microsoft.com/en-us/library/ms141747.aspx
Post #912508
« Prev Topic
|
Next Topic »
20 posts, Page 2 of 2
««
1
2
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
