Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 TempDB...possible source of issues?

Author  Topic 

dhw
Constraint Violating Yak Guru

332 Posts

Posted - 2008-07-11 : 17:45:40
Hello -

We have been experiencing some unexpected system shutdowns on our SQL Server (64bit 2005 w/windows 2003 server 64bit). They "appear" to coincide with some batch processing that occurs automatically at night or when we sometimes run them during the day. After running all the server diagnostics, no errors or issues were reported. However, running Chkdsk some disk errors were reported and then fixed. After that, the batch process ran fine a couple of times. Then today, we experienced two more system shutdowns. Both occured during some batch processing. The batches typically load data from other sources, check and transform data and then rebuild indexes.

Anyway, I am wondering if I should move the TempDB to another drive, just as a way of eliminating this as the source of the issue. Are there any major risks with moving the TempDB on a production server?

Thanks
- will

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2008-07-11 : 17:48:39
I don't see how tempdb could be causing this. But here's how to move it: http://support.microsoft.com/default.aspx?scid=kb;en-us;224071&Product=sql2k

I haven't run into any issues in a production environment with moving tempdb.

Have you opened a case with Microsoft on your shutdown issue?

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

dhw
Constraint Violating Yak Guru

332 Posts

Posted - 2008-07-11 : 17:55:56
Thanks for the info.

I wasn't sure if the tempDB was the culprit, there does appear to be an issue during intensive I/O operations that precede the system shutdowns. Possibly a disk or memory issue? we are trying to get some support - either from our internal help desk or the server vendor (Dell). But the fact that the system shutdowns appear to coincide with the heavy sql operations makes me wonder what they help desk or Dell will tell me.

- will
Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-07-11 : 18:12:24
Is that SQL server 2005 standard edition 64-bit?
Go to Top of Page

dhw
Constraint Violating Yak Guru

332 Posts

Posted - 2008-07-11 : 18:16:31
Sorry for not stating earlier, we have SQL 2005 Enterprise 64bit.
Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-07-11 : 18:22:06
Is your SQL Server build to top notch with recent hot fix and SP.You should get with microsoft for this issue.
Go to Top of Page

dhw
Constraint Violating Yak Guru

332 Posts

Posted - 2008-07-11 : 18:26:17
We don't have the latest cumulative update/patch, but the server does have the latest released SP.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2008-07-11 : 18:32:14
There have been 8 cumulative update packages since the last service pack. In each package contains quite a few bug fixes.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2008-07-11 : 23:28:48
9th just came out.
Go to Top of Page

mfemenel
Professor Frink

1421 Posts

Posted - 2008-07-12 : 07:56:34
Now that you've seen the issue again after fixing things with Check Disk I'd be curious to see if that corruption has appeared again. If it is there you may be dealing with a bad disk.

Mike
"oh, that monkey is going to pay"
Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-07-12 : 11:01:35
Did you run Checkdb of on databases to see any errors caused by bad disks?
Go to Top of Page

dhw
Constraint Violating Yak Guru

332 Posts

Posted - 2008-07-14 : 10:52:15
Yes, since running the Chkdsk and fix, the system has shutdown again after one of the batch processes was run.

And yes, after running the Chkdsk, I ran the DBCC CheckDB and there were no errors reported. In fact, when I ran the DBCC CHeckDB before the chkdsk, there were no errors reported.
Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-07-14 : 11:05:47
So as mentioned, Did you apply patches?
Go to Top of Page

dhw
Constraint Violating Yak Guru

332 Posts

Posted - 2008-07-14 : 14:39:15
No, I haven't been able to apply the patches. I could not get a server outage approved until this coming saturday. I will apply the patches at that time.
Go to Top of Page

mosesofj
Starting Member

2 Posts

Posted - 2008-07-15 : 09:45:37
Have you enabled the Lock Pages in Memory right?

I have experienced performance issues if this is not enabled on 2005 Enterprise (Windows seems to claw back all SQL's memeory, until the service is using ~100MB) - system paging then goes ballistic.

Might be worth checking...

Go to Top of Page

X002548
Not Just a Number

15586 Posts

Posted - 2008-07-15 : 10:21:51
Did you run out of disk?

How big is tempdb now?

Do you shrink the db after your processes?



Brett

8-)

Hint: Want your questions answered fast? Follow the direction in this link
http://weblogs.sqlteam.com/brettk/archive/2005/05/25/5276.aspx

Add yourself!
http://www.frappr.com/sqlteam



Go to Top of Page

dhw
Constraint Violating Yak Guru

332 Posts

Posted - 2008-07-15 : 11:53:55
Yes, I enabled the Lock Pages in Memory. I did that about 10 days ago.

No, we did not run out of disk. The TempDB is about 1.5GB We do have a maintenance plan that (I believe) performs a shrink operation, but I didn't set it up so I will have to check it out.

Thanks for the suggestions.
Go to Top of Page
   

- Advertisement -