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 |
|
lauramayer
Posting Yak Master
152 Posts |
 Posted - 2005-04-21 : 14:24:45
|
| Afternoon,I have a production database here that basically does only reads. It hold indexes that are pointers to another file server.Lately the tempdb is growing by leaps and bounds. As of 2 days ago it was up to 63GB all data processing stopped on the server. We stopped and started the SQL server and that brought it down to 8MB its up to 19GB since then. The index database is right now at 58GB. Is there a reason that this would happen? There haven't been any program changes and users are still accessing it the same way. Can I create some kind of job that checks the size of it on a regular basis and shrinks it?Any suggestions would be welcome.ThanksLaura |
|
|
jason
Posting Yak Master
164 Posts |
Posted - 2005-04-21 : 15:35:55
|
| Interesting...Is this the only database on this instance?You need to run profiler to determine what is creating so many objects within tempdb and why they are not being dropped after use.I wouldn't try to shrink Tempdb while it's online, see the following MS article:http://support.microsoft.com/default.aspx/kb/307487 |
 |
|
|
lauramayer
Posting Yak Master
152 Posts |
Posted - 2005-04-25 : 14:02:40
|
| I am sooo bad at profiler. I never know what to pick. Do you have any recommendations for selections?Thanks so much |
|
|
|
jason
Posting Yak Master
164 Posts |
Posted - 2005-04-25 : 14:24:48
|
| Use the default events, add databaseID to the data columns, and filter the output for database IDs equal to Tempdb's ID. You can choose to save the output to a file or just cache it on the client computer. |
|
|
|
|
|
|
TempDB not clearing