February 25, 2007 at 3:08 am
Hi,
Last friday we doubled the amount of ram on one of our servers from 2 Gig to 4 Gig. Almost immediately delete statements coming from one of our .net services slowed down dramatically to the point where they stopped running. The queries being ran were quite small and ive tested them in QA and they run in a few seconds but from the .net service it runs very slowly and i can see Blocks in EM on the tables its deleting rows from.
Anyone have any ideas ? Nothing else has changed, we were having some resource issuse with the server unable to acquire locks due to a lack of resources. Thats why we upgraded the Ram but it appears to have made things a lot worse. Select Statements seem to run fine.
February 26, 2007 at 3:01 am
the scenario sounds very unlikely, however adding memory is only part of the story, how have you configured this memory and which version of o/s and sql server are you running?
I think it unlikely adding the extra memory will resolve your locks issue, see Ken Henderson's book "Guru's guide to internals..." for details of how sql memory works. Running out of locks sounds to me like your application is at fault , it's not an error I've encountered ( yet ) in many years of working with sql server.
To improve the memory pools you'll have to enable the /3gb switch, awe only increases data cache.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply