September 25, 2015 at 5:38 am
Is there a reason you didn't discuss deployment to the Integration Services Catalog?
September 25, 2015 at 5:57 am
We built a PowerShell utility to deploy ssis packages from TFS. We wanted deployments to be gated. Now we are looking at msbuild options just for build
September 25, 2015 at 6:34 am
cstringham (9/25/2015)
Is there a reason you didn't discuss deployment to the Integration Services Catalog?
Yes, the article is 2.5 years old and only the deployments methods of the package deployment model were in scope.
For project deployment, check this follow-up article:
SSIS Deployments with SQL Server 2012[/url]
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
September 25, 2015 at 8:02 am
We usually build a zip file with folders holding the package and a deployment script that uses the dtutil command. The prod DBA just has to unzip the file to a temp dir and run the script.
easypeasy
September 25, 2015 at 8:03 am
Another way, which is little documented, is using the stored procedure
msdb.dbo.sp_ssis_putpackage
which will allow you automate deployment using TSQL 🙂
September 25, 2015 at 5:27 pm
Nice article! You might want to point out that, on the file system, you can either run the package as a known user (such as scheduled job), or an unknown user (web).
September 28, 2015 at 8:32 am
Please update your article for 2012...Thanks
September 30, 2015 at 3:20 am
Sureindran Nadesan (9/28/2015)
Please update your article for 2012...Thanks
As mentioned before, there's another one that deals with 2012.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
September 30, 2015 at 7:04 am
Thanks for the article. Good informative comments too.
October 15, 2018 at 1:16 pm
We just moved from SQL Server 2008 R2 to 2016, and when trying to work with SSIS.. keep getting errors connecting to SQL Server.. stating that bulk transfrer requires you to be local admin. The user is set up in the server for bulk admin, so how do we get around this error? To give the ability to upload a package I had to go into componet services, DCOMM Config and set up for local access (the remote seems not work work since we use kerberos.)
October 16, 2018 at 6:52 am
dwilliscp - Monday, October 15, 2018 1:16 PMWe just moved from SQL Server 2008 R2 to 2016, and when trying to work with SSIS.. keep getting errors connecting to SQL Server.. stating that bulk transfrer requires you to be local admin. The user is set up in the server for bulk admin, so how do we get around this error? To give the ability to upload a package I had to go into componet services, DCOMM Config and set up for local access (the remote seems not work work since we use kerberos.)
While this article is dated.. it did help to figure out what was needed.
https://www.mssqltips.com/sqlservertip/3086/how-to-resolve-ssis-access-denied-error-in-sql-server-management-studio/
Viewing 11 posts - 16 through 25 (of 25 total)
You must be logged in to reply to this topic. Login to reply