[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 497
  • Last Modified:

LazyWriter Memory Issues; Missing Tables

Our organization is using SQL Server 2005 Standard Edition.  We have recently been experiencing issues with the system, as it appears to run out of memory.  We have a maximum of 2147483647 MB of memory allocated (I  believe this is the default); AWE is not used to allocate memory.

We have found documentation which references the problems we have been experiencing, and most recommend to upgrade to Enterprise Edition, or state an upper memory limit which is approximately 75% lower than the systems memory (8 GB physical RAM, so we'd allocate 6 GB to SQL).

During the last incident when our system became unresponsive, we appeared to have lost several tables when the system was restarted.  This is what I am really interested in.  I believe several of the tables may have been in use when we began to experience errors.  It does appear that it took several hours for our system to become completely unresponsive.  

Any comments on the missing tables would be greatly appreciated.  I have already done a bit of research, but haven't found much insight as to why these tables are no longer in the database.

Thanks In Advance,

- Michael
0
mjs082969
Asked:
mjs082969
1 Solution
 
mjs082969Author Commented:
We no longer believe that the memory problems were causing the loss of tables.  This appears to have been the result of another process.

Thanks!
0

Featured Post

Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now