SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 SQL Server 2012 Forums
 SQL Server Administration (2012)
 SQL 2012 memory errors
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Madhav
Starting Member

USA
38 Posts

Posted - 01/13/2013 :  19:29:56  Show Profile  Reply with Quote
Hi Team,

We have upgrade our SQL Server 2008 R2 server to SQL 2012 SP1(11.0.3000).

We are getting following memeory error after we upgraded to 2012.

Error: 701, Severity: 17, State: 89.
There is insufficient system memory in resource pool 'default' to run this query.

Is this is a bug in SQL 2012?
Appreciate your help.

I found similar issue which is a bug in SQL 2012 RTM and patched in RTM CU5.
http://support.microsoft.com/kb/2769594

Thank you.

Jeff Moden
Aged Yak Warrior

USA
651 Posts

Posted - 01/13/2013 :  22:07:57  Show Profile  Reply with Quote
Do you get the error on more than one query? If yes, then might be a bug in SQL Server. If no, might just be a latent bug in the query.

Also, when you did the migration, did you make sure to bring over all the indexes and rebuild them (which also updates stats).

Last but not least, do you have "always on" or change data capture turned on?

--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for "Row By Agonizing Row".

First step towards the paradigm shift of writing Set Based code:
"Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

When writing schedules, keep the following in mind:
"If you want it real bad, that's the way you'll likely get it."

Edited by - Jeff Moden on 01/13/2013 22:10:34
Go to Top of Page

Madhav
Starting Member

USA
38 Posts

Posted - 01/13/2013 :  22:30:49  Show Profile  Reply with Quote
Thank you Jeff for your reply.

The error is not due to a specific query. I am getting memory errors continuously few hours after restating sql server.

I did not rebuild indexes after upgrading to sql server 2012. Is it mandatory?

This is a standalone server. "Always on" or CDC not enabled on the server but we have replication setup on three databases.

quote:
Originally posted by Jeff Moden

Do you get the error on more than one query? If yes, then might be a bug in SQL Server. If no, might just be a latent bug in the query.

Also, when you did the migration, did you make sure to bring over all the indexes and rebuild them (which also updates stats).

Last but not least, do you have "always on" or change data capture turned on?

--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for "Row By Agonizing Row".

First step towards the paradigm shift of writing Set Based code:
"Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

When writing schedules, keep the following in mind:
"If you want it real bad, that's the way you'll likely get it."

Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.06 seconds. Powered By: Snitz Forums 2000