May 15, 2016 at 6:11 pm
We have a server on 2012 R2 Windows and 2014 SP1 Enterprise SQL. It seems to run out of memory even though when you watch the task manager it doesn't appear to be running out of memory at all. When running a standard db integrity check it crashes and when doing a standard SharePoint crawl it crashes. It has plenty of hard disk space and has 72Gb RAM. Maximum server memory (in MB) was set to 6000. This has been changed to 2147483647 and we are still having the issue.
Kris
May 15, 2016 at 7:35 pm
How do you know it's running out of memory and what is crashing? The server, just SQL? Do you have SharePoint and SQL running on the same box?
Just a couple thoughts...
1. Check your server event viewer (app and server) and your SQL error log.
2. If you need to run an integrity check (assuming you are talking about DBCC CHECKDB) while you are sorting this out, you can add WITH TABLOCK. DBCC CHECKDB makes a snapshot of the DB and checks that. Using WITH TABLOCK skips the snapshot and the check is against the actual DB. Making a snapshot requires memory.
Again, I suspect that the event viewer and error logs will she'd some light on this.
-- Itzik Ben-Gan 2001
May 15, 2016 at 7:59 pm
SharePoint has it's own Web server from the SQL server. In the event log it says "There is insufficient system memory in resource pool 'default' to run this query." and then it crashes SQL. An Integrity check doesn't need to running. It crashes when doing a SharePoint crawl or any SQL maintenance.
Kris
May 16, 2016 at 1:41 pm
When you say "it crashes", what is crashing? The entire instance of SQL Server? The query? The process the application started?
If possible can you run the following and retry the operation:
ALTER RESOURCE GOVERNOR RESET STATISTICS;
If that works you can refer to the following for more info.
http://henkvandervalk.com/sql2014ee-insufficient-system-memory-message
Joie Andrew
"Since 1982"
May 16, 2016 at 1:55 pm
yeah i'm having trouble with the definition of Crashing Sql server;
I'd expect a web page not load with an error, or time out, but saying "crashing Sql Server" means what toy uoi? For me, it implies SQL locking up(deadlocks or blocking?) or actually killing the service and bluescreening the server?
Lowell
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply