November 12, 2012 at 3:11 pm
I am going to build out a SQL 2012 SSIS server to just host integration services and packages (getting off of bad design of people running packgages on my db servers). Any design ideas/gotchas for this. Most of our developers have packages at the file level.
Thanks
November 13, 2012 at 1:09 am
Make sure that the packages are stored and executed on that server.
For example, you can install the SSIS service on machine A on store them on that server, but if you run the SQL Server Agent jobs on machine B, they will be executed on machine B.
If you're going to use SSIS 2012, I would suggest to use the project deployment model and store the packages in the SSIS catalog. This way of working (parameters et cetera) has a bit of a learning curve, but in my opinion they lead to more robust packages and projects. And logging is integrated with built-in reporting on top 🙂
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply