The forum will be unavailable for maintenance at some point from Friday, April 13 at 19:00 EDT until Sunday, April 15 at 23:59 EDT. Downtime will be minimized but the exact timing is unknown.

Having a look at the Microsoft Process Explorer I recognize, that even for a dbsrv11 providing a small database the Virtual Size is in the range of mulitple GBs. On a 32 Bit XP with 2GB Ram it reads 1,6GB Virtual Size for the dbsrv11. On a 64GB Server it reads 40GB and 60GB for two different instances. My observation is that, as soon as the dbsrv11 loads a database the virtual size jumps to the max. What is the reason for this reserved but not already used address space?

Does this affect other programms?

asked 10 Mar '11, 09:23

Martin's gravatar image

accept rate: 14%

The virtual size largely consists of address space reserved for the maximum cache size. Only the "current" cache size has backing store (swap file space) and, likely, RAM associated with it. The rest of the virtual size attributable to the cache has neither backing store nor RAM associated with it. It is just reserved address space and has essentially no impact on the system.

permanent link

answered 10 Mar '11, 16:27

John%20Smirnios's gravatar image

John Smirnios
accept rate: 39%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 10 Mar '11, 09:23

question was seen: 8,200 times

last updated: 10 Mar '11, 16:27