March 26, 2017 at 8:43 am
Hi Experts,
I have been working with SSIS 2008 since last 4 years. Now we are deciding to switch to 2014. Basically with 2008, we have packages having our config information in config files(.XML), i can have the same when we are moving to 2014, but i want to used the SSIS Catalog feature of SSIS 2014.
I had done some googling, but i cannot understand what is the advantage of doing this. Morever i would like to request you guys, if you have some good video link for understandi this i.e. migrating package with XML configuration from 2008 to 2014 (in which we are making used of SSIS Catalog feature of 2014).
Thanks.
March 26, 2017 at 3:04 pm
JackTimber - Sunday, March 26, 2017 8:43 AMHi Experts,I have been working with SSIS 2008 since last 4 years. Now we are deciding to switch to 2014. Basically with 2008, we have packages having our config information in config files(.XML), i can have the same when we are moving to 2014, but i want to used the SSIS Catalog feature of SSIS 2014.
I had done some googling, but i cannot understand what is the advantage of doing this. Morever i would like to request you guys, if you have some good video link for understandi this i.e. migrating package with XML configuration from 2008 to 2014 (in which we are making used of SSIS Catalog feature of 2014).
Thanks.
A few advantages come to mind:
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
March 27, 2017 at 1:51 pm
Phil Parkin - Sunday, March 26, 2017 3:04 PMJackTimber - Sunday, March 26, 2017 8:43 AMHi Experts,I have been working with SSIS 2008 since last 4 years. Now we are deciding to switch to 2014. Basically with 2008, we have packages having our config information in config files(.XML), i can have the same when we are moving to 2014, but i want to used the SSIS Catalog feature of SSIS 2014.
I had done some googling, but i cannot understand what is the advantage of doing this. Morever i would like to request you guys, if you have some good video link for understandi this i.e. migrating package with XML configuration from 2008 to 2014 (in which we are making used of SSIS Catalog feature of 2014).
Thanks.
- Native logging & logging level can be set at runtime.
- Project-scoped parameters and connections
- Configuration using SSISDB 'environments' – no need for external config files.
If you have ever stored a username/password in a configuration file to be used by an SSIS package - then you know how problematic that can become. SSIS Catalog allows you to configure that information at the project or package level in the Catalog as well as overwrite/configure those values in SQL Server Agent very easily.
Another nice feature is being able to create a new project from an existing project that has already been deployed. The new project can then be modified and deployed as a different project - or as an update to the existing project.
Manually executing projects from the catalog runs those packages on the server...not on your workstation.
And finally, you have the reporting feature that is available from the catalog that will make it much easier to identify issues and see what tasks are taking the longest to process.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply