May 22, 2002 at 6:39 am
I have a test server that has been upgraded from SQL7 SP3 to SQL2k SP2. This server runs a data warehouse ETL and cube reprocessing job in parallel with our production system. On the production server, TEMPDB is approx 5GB. On the test server, the same process running in parallel has pushed TEMPDB out to over 14GB. Ouch! To add, both test and prod TEMPDBs are set to auto-grow 10%, I have shrunk both TEMPDBs before running the process, and there are no other processes running on these servers.
Has anyone had similar problem/experience after a SQL2k upgrade? Is there any way to reduce the TEMPDB size?
Thanks...Jay
Does anyone know what is going on?
May 22, 2002 at 12:45 pm
How big is the transaction log files for the actual database for each. I thought I read somewhere that 2000 uses tempdb more extensively than 7 did.
I'll try to find where I saw that.
Tom Goltl
May 23, 2002 at 1:03 am
The transaction logs are defined as 100mb and did not auto-grow. Perhaps this is due to the different hardware configurations between the servers? The production server is a 4x P3-500Mhz 2Gb RAM. The test server is 1x P4-1.5Ghz 1Gb RAM.
Thanks....
May 23, 2002 at 5:49 am
Is it still growing, and what is the process doing? I have not seen anything on my 2000 server with tempdb that is different from the behavior on a 7 server running the exact same processes.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
May 24, 2002 at 6:41 am
This must have been something to do with the upgrade process somehow. I shrunk the tempdbs back to 5GB and reran our processing on both test servers. No TEMPDB increases this time. Strange...
Thanks
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply