http://choirulamri.org born to train, forced to code::SQL Server, SharePoint, .Net, Business Intelligence Sat, 21 Aug 2010 02:02:47 +0000 en hourly 1 http://wordpress.org/?v=3.0 http://choirulamri.org/archives/513 http://choirulamri.org/archives/513#comments Sat, 21 Aug 2010 02:02:47 +0000 mca http://choirulamri.org/archives/513 http://choirulamri.org/archives/513/feed 0 http://choirulamri.org/archives/369 http://choirulamri.org/archives/369#comments Sat, 03 Jan 2009 09:46:00 +0000 mca http://choirulamri.org/archives/369 Moral of the story: make sure you have automated way to manage transaction log growth. There are 2 way to shrink the log:

• Detach database, delete the big log, and re-attach without log file. SQL Server will create a new, fresh log file with minimum initial size. It is 2MB by default. Disadvantage: the database will not be available during the process. Offline duration depends on how fast is the detach – attach operation takes time.
• Better approach: use SHRINKFILE of DBCC command. This is better because I do not need to bring the system OFF.

Regardless of the approach, make sure to do full database backup. Shrinking the log deletes historical transaction that may be needed to restore database to specific point of time. Just in case, make sure to do full backup. You have been warned right :). These are the steps to shrink a huge log file:]]> http://choirulamri.org/archives/369/feed 1 http://choirulamri.org/archives/165 http://choirulamri.org/archives/165#comments Wed, 22 Oct 2008 07:17:41 +0000 mca http://choirulamri.org/archives/165 http://choirulamri.org/archives/165/feed 2