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 |
|
carumuga
Posting Yak Master
174 Posts |
 Posted - 2009-08-11 : 07:03:57
|
| In one of my Job, my DBA has used the command DBCC ShrinkFile to shrink my tempdb. Since it was running for quite long period of time, I was forced to cancel the step configured in the job. My DBA suggested that "Some connection must have been holding onto tempdb.So order will be kill connections, shrink tempdb, kill connections again."Can you please tell me what that actually mean. Is there a way to identify the blocking connections.Thanks in advance. |
|
|
lionofdezert
Aged Yak Warrior
885 Posts |
Posted - 2009-08-11 : 07:57:24
|
| http://connectsql.blogspot.com/2009/07/in-environment-where-more-then-one.html |
 |
|
|
carumuga
Posting Yak Master
174 Posts |
Posted - 2009-08-11 : 22:58:20
|
| Prior to shrinkfile step, i have added kill statement which identify the processes from sysprocesses table, the DBCC shrinkfile step still hangs, and i have to run it manually to fix the issue.May I know the root cause of the issue as it doesnt get executed from the job.Thanks in advance. |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2009-08-12 : 11:35:50
|
| is still in use most likely. processes can connect faster than u can kill them.more important to identify what is growing tempdb so much. may need to allocate more storage. it is growing because work is happening in it.by the way, it is rebuilt at original size when SQL Server service restarts |
|
|
|
|
|
|
dbcc shrinkfile