June 2, 2009 at 7:45 am
Hello, After upgrading to SQL 2008 x64 from SQL 2000 we randomly get memory issues in which we have to restart the SQL service in order to bring SQL back online. We are running a Windows 2003 server x64 w/ 8GB RAM. SQL 2008 was installed using default settings with the exception of files locations. I have checked all SQL memory parameters like the max/min server memory, min memory per query and such. All are set to the default.
Here is the event log error that starts everything.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:Server
Event ID:701
Date:6/1/2009
Time:4:35:10 PM
User:N/A
Computer:RRSRV05
Description:
There is insufficient system memory in resource pool 'internal' to run this query.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: bd 02 00 00 11 00 00 00 ½.......
0008: 08 00 00 00 52 00 52 00 ....R.R.
0010: 53 00 52 00 56 00 30 00 S.R.V.0.
0018: 35 00 00 00 0c 00 00 00 5.......
0020: 52 00 65 00 6d 00 69 00 R.e.m.i.
0028: 74 00 52 00 65 00 70 00 t.R.e.p.
0030: 31 00 39 00 34 00 00 00 1.9.4...
Any ideas? I am currently parsing through the error log but not quite sure what I should be looking for.
I am posting this in the newbie section because I am exactly that and struggling. :crazy:
Thanks in advance for your help!
June 2, 2009 at 9:34 am
Here is a a Connect item about this issue. It doesn't really provide an real answer, but does recommend that you lower the Max Server memory setting to make sure the OS has enough memory. You should probably have max server memory no higher then 6GB.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
June 2, 2009 at 10:27 am
Makes sense to me. I will cut the max server memory down to 6144 MB instead of the standard 2147483647 MB. I am guessing this will either fix the problem or we will see the problem quicker since it will not have the 8GB RAM plus the 16 GB paging file to go through before it starts tossing errors out.
I will let you know how it goes. Thanks for the help.
June 5, 2009 at 10:28 am
Day 3. So far so good. Thanks for the tip!
June 6, 2009 at 10:46 pm
Great. I'm glad that this seems to have worked. I hope the problem is solved.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply