June 23, 2014 at 11:55 pm
Hi All,
I am currently designing a SSIS package that will migrate data from Syabse to Sql server. I am in need of your suggestion if these packages are to be deployed to file system (as this is one time run for migrating data) or to SSIS catalog or to Sql server. Please help.
Also, I have not changed the default protection level value in packages during design time and would like to know if I have to change it while handling the deployment using DTutil (yes, i need to deploy & execute using command line utilities).
Please note that I do not have access to PROD, UAT environments and deployment team will use my BAT file that is expected to deploy and execute the packages. Please let me know your suggestions and best practices to be followed in this case.
Thanks.
Regards,
Suresh Arumugam
June 24, 2014 at 12:01 am
If you want to deploy to the SSIS catalog, your project needs to be in the project deployment model.
In that case you cannot deploy using DTUTIL but there are other options:
SSIS Deployments with SQL Server 2012[/url]
If you want to use DTUTIL, you need to use the package deployment model and you can deploy to either SQL Server or the file system.
If you store passwords inside the package, you need to change the protection level. Either change it to EncryptSensitiveWithPassword and supply a password when running the packages or change it to DontSaveSensitive and use package configurations.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
June 24, 2014 at 2:52 am
Thanks Koen. I am planning to use the dtutil utility to deploy to file system and dtExec to execute the packages.
By the way, would there be any issues if I just leave the default protection level what is there in the package design time and just pass other config (log path, source , destination DB connections etc) details during DtExec? Do you think package execution will fail?
dev team does not have access to Prod environments. So, I wanted to go with command line utility options and deployment team can just run one bat file and ensure packages are deployed & executed.
Regards,
Suresh Arumugam
June 24, 2014 at 3:00 am
If you don't specify any package configurations in the package itself, it should normally run successfully.
You can leave the default protection level, but you will get some warnings about SSIS not being able to decrypt some information.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply