Do I need to convert my SSIS project in VS and deploy it first somehow on my server?
I know that an SSIS project creates a package.dtsx by default so do I need to publish this so that I can see it in SQL Server Management Studio under my Integration Services section? I do not see any packages and get an error when trying to click on the folders "filesystem" or "MDSB" under my SSIS connection in Server Management Studio....likewise when I try creating a job, I try to browse to packages and get a cryptic error, probably because my package isn't showing up in Server Management Studio yet.
The error I get while trying to import packages is saying it can't enumerate or something when I try to browse to my package location. I also get an error saying "encryption not supported on SQL Server (Microsoft Native client) when trying to browse to my package location when trying to import my package in SSIS in Server Management Studio.
Two (different) answers:
1) You don't have to do anything, you can just copy .dtsx file to the server and run it using DTEXEC command line, or schedule it using Agent directly from the file system. While running, it will appear in SSMS 'Running Packages' node, but it will not be in 'Stored Packages' node since it is not stored in SSIS Server.
2) If you want package to appear in 'Stored Packages' in SSMS, you do need to deploy them to the server. Several options exists how to do this: Save Copy As.. command in VS, deployment wizard, dtutil.exe tool. See BOL for more info.
|||Thanks a lot!
No comments:
Post a Comment