Shrinking file issue – Dependency of tran_log file.


Recently I observed an issue where we were trying to shrink a database file [Shrinking is not recommended in Production environment as it will cause fragmentation] and SQL Server was not shrinking the file. There was no specific error to identify the reason for this behavior.

We did some R&D and finally observed that the tran_log file was really small and almost full and this was the reason for the Shrink operation to fail.

This is one of the behavior which might happen to your environment too, incase the transaction log is too small.

I am curious to understand if anyone of you might have faced this before.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s