October 22, 2015 at 1:05 pm
This is my first post here and after much googling I could not find an answer.
I am a vendor working on a SQL Server 2008 instance that is running on a VM. I do not know the specifics of the VM. Both SQL Server and SSIS packages are running on this machine. SQL Server is configured to use 10GB of the 16GB installed in the VM. What I am noticing is that when my ssis packages run every half hour, the DTExec.exe process is running up and taking all of the memory. SO much so that I can sit and watch the sqlservr.exe start to decrease. Within a couple of minutes the DTExec.exe process is consuming over 15GB of memory and sqlservr.exe is running around 300-400mb. Once the packages stop...everything drops down to pretty much 0% memory utilization and sqlserver will gradually run back up to the 10GB. Every half hour the same scenario happens. This did not happen in the past. In fact I had them add memory due to the SSIS packages having to read and write to disk. THey added the memory and everything ran fine and the BuffersSpooled counter stayed at 0. Now I am noticing that it is just taking over the memory when the DTExec.exe runs.
ANy help would be greatly appreciated. As I mentioned above..I do not have info on the actual VM setup nor am I an expert in that arena. ANy input as far as what questions to ask the VM provider would help. I am assuming that something was changed there to allow this.
Thanks.
October 22, 2015 at 1:13 pm
Been there seen that, but don't know of any way to avoid the high memory usage.
FYI, limiting SQL Server to no more than X MB will not help in any way. Limiting SQL Server to no more than X MB only affects the database engine, not the other services, such as SSIS.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
October 22, 2015 at 2:41 pm
Thanks Alvin. I have just never seen SQL Server give up memory to anything else. Normally the issue is that SQL Server is taking up all of the memory. As I stated..that was originally the case. Before I got them to add memory..SQL Server was using 7 GB and when SSIS packages would run..they would end up reading and writing to disk due to SQL Server taking up all of the memory and not releasing any to the DTExec process. In fact I had to lower the max memory for SQL Server down to 4 GB so the packages could run in memory. This has me boggled.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply