SQL server tempdb expansion,shrinking
Hi All,
I have a BCP load process which failed last night saying short of space at tempdb.
When I had a look this morning I have more than 120 GB free on the volume where tempdb is located. The total size of volume is 300GB.
The files on tempdb device are still of size 10GB. I configured them with "unrestricted Growth" so they should take remaining 120GB free when needed.
My question is "Why do I have an error in the first place"?
Does tempdb files shrink automatically after the transaction using them has finished?
Can I use any DMV to locate space usage for last 24 hours? If not how do I know what went wrong with last night's process?
Thanks
I have a BCP load process which failed last night saying short of space at tempdb.
When I had a look this morning I have more than 120 GB free on the volume where tempdb is located. The total size of volume is 300GB.
The files on tempdb device are still of size 10GB. I configured them with "unrestricted Growth" so they should take remaining 120GB free when needed.
My question is "Why do I have an error in the first place"?
Does tempdb files shrink automatically after the transaction using them has finished?
Can I use any DMV to locate space usage for last 24 hours? If not how do I know what went wrong with last night's process?
Thanks
Tuning your complex queries either by breaking them into pieces or by adding more indexes could actually improve the performance and reduce load on tempdb.
ASKER
Could you please answer to my specific queries below.
My question is "Why do I have an error in the first place"?
Does tempdb files shrink automatically after the transaction using them has finished?
Can I use any DMV to locate space usage for last 24 hours? If not how do I know what went wrong with last night's process?
My question is "Why do I have an error in the first place"?
Does tempdb files shrink automatically after the transaction using them has finished?
Can I use any DMV to locate space usage for last 24 hours? If not how do I know what went wrong with last night's process?
Does tempdb files shrink automatically after the transaction using them has finished?
No. You cannot set Tempdb to Auto-Shrink.
No. You cannot set Tempdb to Auto-Shrink.
ASKER
OK that's great! So the question is, why did the tempdb didn't expand when it is set for autogrow and lot of space was free on the volume.
Is there any DMV which will show growth of tempdb file?
Thanks
Is there any DMV which will show growth of tempdb file?
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Yes it would shrink automatically once the transaction gets over
Care to post some documentation to back that up? As I stated previously, you cannot set the tempdb to Auto-Shrink.
Care to post some documentation to back that up? As I stated previously, you cannot set the tempdb to Auto-Shrink.
Agreed acperkins!
I think I wrote wrong statement earlier. There are 2 things:
1.> Size of tempdb
2.> Free space in tempdb
With end of each transaction, space allocated to internal objects of that transaction within tempdb would be released thus free space in temp db would increase.
Size you are right, it won't change automatically until we restart SQL server or shrink explicitly by dbcc shrinkdatabase or shrinkfile command. Somehow I messed up between free space and size. I apologize about that.
I think I wrote wrong statement earlier. There are 2 things:
1.> Size of tempdb
2.> Free space in tempdb
With end of each transaction, space allocated to internal objects of that transaction within tempdb would be released thus free space in temp db would increase.
Size you are right, it won't change automatically until we restart SQL server or shrink explicitly by dbcc shrinkdatabase or shrinkfile command. Somehow I messed up between free space and size. I apologize about that.
>> have a BCP load process which failed last night saying short of space at tempdb. <<
Please post the *exact* error message(s).
And review the SQL Server error log; you very likely have additional error msgs there.
Verify that the tempdb *log* file is on a drive with additional space available, and that it is set to autogrow, and set to a fixed amount vs a percentage amount (such as 100M rather than 10%).
Please post the *exact* error message(s).
And review the SQL Server error log; you very likely have additional error msgs there.
Verify that the tempdb *log* file is on a drive with additional space available, and that it is set to autogrow, and set to a fixed amount vs a percentage amount (such as 100M rather than 10%).
If the BCP failed I expect it would have initiated a rollback reversing any changes to the temp database ....
1.> Temp tables
2.> Large table variables
3.> Intermediate query results during complex queries
4.> image of objects if you have enabled snapshot isolation level for your database/server
5.> Cursor processing..
6.> Other metadata
To control the size of tempdb you need to observe usage of all these features in your BCP program. Might be possible, there is some performance issue with your queries in BCP load process or you are using temp tables excessively.