Exploding TEMPDB

petergjones · Post by **petergjones** » Wed Jun 16, 2004 5:21 pm

Not a big problem but since installing vault we've noticed our TEMPDB grows to 500mb each day. This is filling our C: drive so we need to extend/move this onto D:.

I was curious if anyone else has noticed this ? Maybe it's not Vault but we haven't installed anything else lately.

Post by **jclausius** » Wed Jun 16, 2004 9:06 pm

Vault will use tempdb during normal operations.

Without having complete information, here are some other questions off the top of my head.

- Is the DB size 500 MB or is it the size of the .mdf?
- Does a shrink bring it back?
- Is it possible the tempdb is set to auto grow, and the growth rate is large? What about settings on model db?

Some other things to check (note, some of the usenet links are for SQL 7, but I thought it would be useful to include them anyway):

- http://support.microsoft.com/default.as ... us;Q307487

- http://groups.google.com/groups?q=%22sq ... com&rnum=1

- http://groups.google.com/groups?hl=en&l ... 6rnum%3D21

petergjones · Post by **petergjones** » Sun Jun 20, 2004 4:59 pm

I'll pass this on to our DBA. We have found that the backups at 2am schrunk TEMPDB to 2meg and by 11am, it was 1 gig!

It could be some other process doing this (maybe sharepoint indexing) so we'll turn this off and see what happens tonight.

Thanks

Post by **jclausius** » Mon Jun 21, 2004 6:58 am

1) What version of Vault are you currently using?
2) Can you find out the result for:

SELECT COUNT(*) FROM sgvault.dbo.tblsessions
SELECT COUNT(*) FROM sgvault.dbo.tblsessionrellocks

3) Do you happen to use the Vault / VS.Net IDE Client?

4) Do you happen to use a Vault extension for Continuous Integration?

petergjones · Post by **petergjones** » Mon Jun 21, 2004 2:34 pm

Verion 2.0.3

Queries returned 1 & 0 and then 2 & 2 so I guess this is veriable.

Yes we use the VS.Net integration and the Vault client.

Not sure what you mean by Vault Extension but I use the command line vault.exe via NAnt scripts to do CI. It's checking project history for a dozen projects every hour or less.

Thanks

Post by **jclausius** » Mon Jun 21, 2004 3:06 pm

There is a side-effect of using a client which does not log out of Vault. Over time, these logins become back logged due to a large session timeout. It is plausible this scenario could build up the database's log file.

However, the results of your queries indicate this is not the problem.