Automated Restart

• Don Reid

  SSC Journeyman

  Points: 95

  More actions

  September 14, 2004 at 10:33 am

  #162625

  Ok, I am an admitted novice on SQL Server.  However, I am running an application that sits on top of SQL server for storage and calculation.  Whenever this tool accesses SQL Server 2000 SQL Server grabs memory for the process.  One problem, our problem with our application I am sure, is that SQL does not release the memory.  After a few days use the VM and Memory usage rises to the Gigabyte levels.  When I restart SQL Server, it returns to about 50 MB.  Here is my question.  Is there an automated way to schedule a restart of the server, or release of memory each night about midnight.  This isn't a mission critical server, it is only used for this application and is not needed at that time.  Can anyone offer a suggestion?

   

  Thanks,

   

  Don

• Gé Brander

  SSCarpal Tunnel

  Points: 4353

  More actions

  September 14, 2004 at 11:59 pm

  #523100

  You can use the 'max memory' and 'min memory' setting. This way, the server has always a minimum amount of memory available and will not take more than you set.

  In Enterprise Manager right click the server and choose properties and look on the Memory tab.

• Don Reid

  SSC Journeyman

  Points: 95

  More actions

  September 15, 2004 at 12:03 am

  #523101

  Thanks,

       I considered that at first, but I am concerned about performance degradation and other side effects that may affect our tool.  We run some pretty large jobs that will take all the memory needed.  That in itself isn't a problem, our tool just does not let SQL release the memory once the job is done.  Therein lies my problem.

   

  Don

• fhanlon

  SSChampion

  Points: 13131

  More actions

  September 15, 2004 at 8:17 am

  #523172

  All our SQL Server installations run on their own server.  Any application that uses SQL Server runs on another server, that includes IIS or Apache.   If the server has 4 G  I don't care if SQL Server takes 3.7 G and never releases it.  The application run on their own machine and their memory usage is not a concern to SQL Server.  If your application runs on the same physical server as SQL Server reconsider this and think about moving all applications except SQL Server off of this machine.

  Francis

• Don Reid

  SSC Journeyman

  Points: 95

  More actions

  September 15, 2004 at 9:17 am

  #523184

  I should probably elaborate a little.  This server is a training server for customers and internal employees.  Budgetary restrictions inhibit the idea of two servers.  This is something that has been considered, but will still not solve the problem.  There is another layer that I have not discussed, my fault.  We also use Analysis Service with a repository set on SQL server.  When SQL server is bogged down, the OLAP is bogged down.  Also, even though our application uses SQL as a data repository, it also uses it as a calculation engine.  So a lot of the processing is happening with SQL.  Just splitting servers will not solve the issue.  Apparently the best route will be to request a change in our own application, rather than set an automated restart.  I suspected this was easier said than done.

   

  DOn