April 3, 2014 at 12:47 am
While inserting the data cpu usage goes high.
From the front end we are just inserting the data to the table. while inserting the memory taken by sql server is almost full,
Max config for memory is 2GB for sql in 4GB of RAM.
why SQL server is taking all memory.-
while running the insert query almost cpu reaches 80-90% every time why this is so?
April 3, 2014 at 12:50 am
By design, normal, documented behaviour. SQL will take all the memory it is allowed to use.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 3, 2014 at 3:53 am
GilaMonster (4/3/2014)
By design, normal, documented behaviour. SQL will take all the memory it is allowed to use.
Thanks Gail for quick replay.
Then the Insert should be that much fast right if it is one transaction?
My question is if for the one transaction it utilise all memory then how about other queries it will be internally splitting the memory?
how the weightage of query? how sql will decide about each transactions weightage.
April 3, 2014 at 10:09 am
SQL manages its own memory very well. There's a hell of a lot to it. If you want the details, get a copy of "Troubleshooting SQL Server: A guide for the accidental DBA" and read chapter 4.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 4, 2014 at 4:29 am
Thanks for that reference book, it is really nice.:-)
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply