April 8, 2005 at 1:53 am
Hi there,
I'm at a loss right now. Situation: I have 2 servers, both similar configurations with W2003 and SQL Server Standard Edition with sp3. Hardwareconfig is practically identical: 4 processors are on server1 are slightly faster then those on server2(3400 vs 3200), 3Gb internal RAM, plenty of diskspace.
We have an apl which runs a heavy batch involving several 100 million records, heavily laced with virtual tables.
On server2(testserver) this batchproces runs without problem. On server1(future production) this proces suffers from an exploding tempdb: the tempdb keeps eating up diskspace untill there is none left. This does not happen at the same step in the process, it differs from run to run, and wildly at that. I cannot see a pattern. Also, it does not happen always.
What can be the cause of such DIFFERENT behaviour? I know what MAY cause the tempdb exploding, I just don't know how to solve this erratic behaviour. What thing should I check?
Any hints are very apreciated.
TIA,
Hans Brouwer
Greetz,
Hans Brouwer
April 8, 2005 at 3:17 am
Hi Hans,
I can't help you with the erratic behaviour but I can give you a solution. Set the tempdb on Restricted File Growth. Whenever the max size of the db is reached, SQL-S will automaticly shrink the files. (Do this for both the MDF and the LOG)
Cheers,
Ronald
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply