July 20, 2017 at 9:23 am
Hi,
We've got a current sql server production environment running and I'm trying to run an ssis package and its giving me an error message that suggests ssis isnt installed on the current host.
if we go through the installation setup and install ssis, is there ay side-effetcts to our current slq installation we need to be aware of?
My understanding is its a separate service and the instattion setup clearly states a shared feature can be setup alongside an current instance.
please advice and thanks for your help.
July 20, 2017 at 11:17 am
We have things set up that way where I work.
The only thing you need to be careful of is that SSIS operates in separate memory space than SQL Server. That is, if you have a server with 64 GB of memory total, and you have SQL configured to use 60 GB, this means that SSIS AND your OS need to share the remaining 4 GB. This is not a lot of memory for them to share. Especially if you are pulling in large data sets inside SSIS.
But, if you are pulling small data sets and not doing a lot of data manipulation, you will likely be fine.
If you do not have a lot of spare memory, I would set up some sort of "job monitor" that would keep track of long running jobs. Where I work, we have a nightly data load into our data warehouse that normally takes 2 hours. If it runs longer than 2 hours, it sends alerts to all of the DBA's. We also have hourly data loads that take about 5 minutes to complete. If it runs longer than 5 minutes, alerts go out to the DBA's.
The reason it sometimes takes longer - the server ran out of memory. That made our hourly load (the 5 minute load) run for 8 hours.
So do be sure to monitor your memory usage. The SSIS packages also use separate CPU than SQL Server. So if you have a low resource system, you may notice a performance impact on the live server of having SSIS installed.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
July 21, 2017 at 1:53 am
I'll take a note of all of that. Thanks for the advice.
July 21, 2017 at 5:39 am
The real question is, why do you think you need SSIS? What will you actually be using it for? It may be that you don't actually need SSIS to do what you want to do.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply