March 22, 2016 at 3:57 pm
We have a SQL server that mainly hosts data warehouse databases.
And there are a lot of SSIS packages to run nightly.
And recently the server was crashed and rebooted automatically during night. We cannot find the reason.
The only thing we find out is there are some packages to run during that time.
But the SSIS packages have been run for half a year now, then most of time there are no problem. We don't know why that caused the failure of crash of the server a couple of times recently.
Any troubleshoot tips?
Also since these are 2008 SQL, we need to upgrade them soon. Should we put SSIS in delicated server separate from database server?
I see it can be speed up if it has its own dedicated resources, but I am also concerned if it could be slow down because databases that either source or destination is not on local server, but have to cross network, will that slow down the SSIS too?
March 22, 2016 at 4:48 pm
Hi,
Please check memory configuration, SQL server is aggressive with memory allocation
and can occupy most of the memory, SSIS has to fight for memory allocated outside of SQL server.
Imho this is a first step to check.
Please check the BufferTempStoragePath location, the system TEMP is set as the default where SSIS can page the buffers. You need to make sure that there's enough place for that.
Regards
Mike
March 22, 2016 at 5:27 pm
The Ram is total 96 GB. The max memory we set is 83 GB.
Today when we tried to login to the server at day time, we found it is slow to remote in to load the desktop of the server. There is a ssis package running at that time.
And our network admin notice at that time the CPU is 100%.
Does SSIS use a lot of CPU?
Right now the server has 8 cores and 16 hyperthread.
Thanks
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply