SQL Server not releasing memory

Question

Hello,
I have created one stored procedure, which inserts data into 1 table.
It inserts around 1 million records at a time using XML input.
Problem is with SQL server memory I think. When I run this stored procedure and check the performance in the morning when server is not so busy, it finishes with less than 10 seconds.\
However, if I continuously test this stored procedure multiple times, it gives huge variation in performance.
Also, I call this stored procedure from C# front and there I have made sure that I am disposing Connection object every time.
After few runs, I have to restart my server computer as it doesn't allow me to run any of the query on that server.
So my question is :
What is that which occupies whole server memory?
Is there any thing which I can write in stored procedure to release memory once it is done?
Please assist me on this.
Thank you,
Mittal.

Answer 1

Hello,
I have created one stored procedure, which inserts data into 1 table.
It inserts around 1 million records at a time using XML input.
Problem is with SQL server memory I think. When I run this stored procedure and check the performance in the morning when server is not so busy, it finishes with less than 10 seconds.\
However, if I continuously test this stored procedure multiple times, it gives huge variation in performance.
Also, I call this stored procedure from C# front and there I have made sure that I am disposing Connection object every time.
After few runs, I have to restart my server computer as it doesn't allow me to run any of the query on that server.
So my question is :
What is that which occupies whole server memory?
Is there any thing which I can write in stored procedure to release memory once it is done?
Please assist me on this.
Thank you,
Mittal.
>> 1. What is that which occupies whole server memory?
Probably your application or the other application, but this need to be checked and not guess! Your machine execute hundreds if not hundreds of thousands applications on the same time! most of them are services that you do not see any
GUI. The SQL Server itself might execute hundreds if not hundreds of thousands transactions and these might interfere one another (lock tables or rows, use the same resources and so on).
* as a first test you should try to execute the query using a more reliable application like the SSMS. I recommend to try execute the query throw the SSMS several times and check the behavior.
>> 2. Is there any thing which I can write in stored procedure to release memory once it is done?
There are several option to free memory that used by SQL Server, but do you really need it?!? This is probably not the solution for your case. in the best option it will only give you a workaround.
* SQL Server do not use more resources that you let it (configure it). If you are using SQL EXPRESS than you have some limitations regarding the resources (for example memory and CPU and database size...).
Make sure that you configure the SQL Server not to use to much resources, so that other applications like the operating system will have what they need! There is no logic in restart the machine if the only
problem is with specific application (unless you have problems like memory leak which in rare cases can not be treat otherwise)
http://mrbool.com/how-to-clean-up-memory-sql-server/29242
https://msdn.microsoft.com/en-us/library/ms178067.aspx?f=255&MSPPError=-2147217396
** start monitor the SQL Server resources, locks and waits
https://technet.microsoft.com/en-us/library/aa213039(v=sql.80).aspx
http://www.brentozar.com/sql/locking-and-blocking-in-sql-server/
*** Give us more information instead of stories :-)
Post codes that you use, post DDL+DML and so on.
  Ronen Ariely
 [Personal Site]    [Blog]    [Facebook]