Video Screencast Help

Vault Store DB unusually big.

Created: 11 Jun 2013 • Updated: 24 Jun 2013 | 4 comments
The Boulon's picture
This issue has been solved. See solution.

Hello,

 

My customer archived like 17 millions files some days ago.

When looking at the VS DB, it looks unusually big, like 58,3Gb!

 

Is this a normal behaviour?

 

Thx

 

Olivier

Operating Systems:

Comments 4 CommentsJump to latest comment

JesusWept3's picture

Take a look at this query here and run it against the vault store table
It will tell you which table is taking up the most space, and it could possibly be an index

http://therightstuff.de/CommentView,guid,df930155-f60f-4f56-ab33-f1352ff091a1.aspx

But really it could be a couple of things like you could be looking at the translogs and db combined
or more likely than not, someone set the AutoGrowth too hight
 

The Boulon's picture

Indeed the SavesetProperty is taking a lot of place.

 
name                  rows        reserved           data               index_size         unused
 
SavesetProperty   18008136    40354736 KB        35717640 KB        4632080 KB         5016 KB
 

Any idea why?

 

 

JesusWept3's picture

Are you doing a lot of FSA perchance?
I checked on a DB that i have with 42 million rows (so over twice as many as yours
But uses 1.5GB data as opposed to your 35GB and 730MB indexes as opposed to your 4.6GB

And based on the post rob linked to, it would most likely be coming from these Properties columns