Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Adding RAM to SQL 2005 SE, but 2000 Compatibility Expand / Collapse
Author
Message
Posted Monday, July 29, 2013 7:53 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Wednesday, September 10, 2014 1:06 PM
Points: 2,829, Visits: 8,479
We have a Windows Sever 2003 server, running SQL 2005 Standard Edition SP3 with 4 Gig RAM. I would like to increase the RAM. However some of the databases are running in 2000 compatibility mode, due to legacy code not supported in 2005.

Will processes running in those databases benefit from additional RAM ?



Post #1478598
Posted Monday, July 29, 2013 8:03 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 9:00 AM
Points: 43,001, Visits: 36,157
All that compatibility level does is change the way that the query processor executes some specific SQL statements, ones that changed behaviour between 2000 and 2005 (and whether or not some constructs will parse or not). That's all.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1478605
Posted Monday, July 29, 2013 8:17 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Wednesday, September 10, 2014 1:06 PM
Points: 2,829, Visits: 8,479
Thanks.

I was prompted to look at RAM as a solution after getting this error message when trying to run a stored procedure:

An error occurred while executing batch. Error message is: Exception of type 'System.OutOfMemoryException' was thrown.



Post #1478610
Posted Monday, July 29, 2013 8:51 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 9:00 AM
Points: 43,001, Visits: 36,157
That's a client error. not a server error. Sql server isn't written in .Net and yet that's a .net error.

You'll get that if you're pulling a huge resultset into Management Studio and you run your client machine out of memory (or just SSMS, it's a 32-bit app, so it can use 2GB memory at most)



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1478629
Posted Monday, July 29, 2013 8:58 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Wednesday, September 10, 2014 1:06 PM
Points: 2,829, Visits: 8,479
Thanks. Sounds like I am misplacing the blame.


Post #1478634
Posted Monday, July 29, 2013 9:18 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 9:00 AM
Points: 43,001, Visits: 36,157
Oh, and don't run Management Studio on the server and run queries that return huge resultsets....


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1478642
Posted Monday, July 29, 2013 9:41 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Wednesday, September 10, 2014 1:06 PM
Points: 2,829, Visits: 8,479
GilaMonster (7/29/2013)
Oh, and don't run Management Studio on the server and run queries that return huge resultsets....


I was starting to troubleshoot a timeout error that an application is having. I suppose it must be doing something similar.



Post #1478651
Posted Monday, July 29, 2013 10:05 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 9:00 AM
Points: 43,001, Visits: 36,157
If the app's pulling enough data to make Management Studio run out of memory, I'm not particularly surprised that it's timing out. That'll be a lot of data.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1478661
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse