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.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-08-30 : 08:37:26
|
| Jamie writes "Can anybody help, I am IT administrator for a telesales company who run Goldmine on the client workstations, and SQL server for its database engine.The SQL server is a compaq proliant 570 (quad processor, 2GB ram, 140GB disk space) running on windows 2000 Advanced server SP2, and SQL 2000.The database is approx 4gb with 900,000 records.The situation I find myself in is this, every so often the server completetly freezes and the only thing I can do is switch it off, once rebooted I have discovered quite a few event viewer error messages reporting that the "Log file for database tempdb is Full", and I suspect that this may be the cause of my server crashesHas anybody come across this before and if so how did you correct the problem.Thanks in advanceJamie" |
|
|
royv
Constraint Violating Yak Guru
455 Posts |
Posted - 2002-08-30 : 10:23:44
|
| Well if the tempdb log file is getting full, the quick solution is, because you have a huge hard drive, is to increase the log file size for tempdb. Secondly, and I'm guessing here, if you are using temp tables to store all these 900000 records frequently, then increasing the log size makes sense, but you should look at your application and see if there is anything that can be done to use table variables. Table variables are completely in memory and do not require and disk activity.*************************Someone done told you wrong! |
 |
|
|
KnooKie
Aged Yak Warrior
623 Posts |
Posted - 2002-08-30 : 11:36:23
|
| The front-end application may be opening recordsets but not closing them when it's finished with them. These recordsets i believe can reside in the tempdb database.Paul |
|
|
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
Posted - 2002-09-01 : 16:47:03
|
| Look at Tempdb size, if you really suspect it. Consider increasing the size. Ensure that it is set to automatic growth - consider for yourself what the best setting would be for your environment. If you have that much disk space, consider creating tempdb at - say - 512 MB (or even 4 GB - same size as your DB, if you can afford it), and growing at 512 MB , to ensure that each growth buys you time for fast using app's...Also check whether a max (restrict file growth) setting has been set, and consider chaning that...Also, ensure that you do actually have space - is your temp DB on the drive that has space? If you have a 140 GB D drive, but temp db is growing and running out of space on, say , C: - well move it ...HTH |
|
|
|
|
|
|
|
|
TempDB log file