DBCC SHRINKFILE causing massive disk queues

26 Jan 2006 3:59 PM

DC

Hi,

I am using a database with massive update and insert action and
therefore shrink logfiles every 15 minutes since the logs explode
otherwise. Shrinking the logs results in a massive performance hit and
usually takes about three minutes with huge disk queues.

Is there any way to shrink the logs with lesser queues?

TIA for any idea,

Regards
DC

26 Jan 2006 4:39 PM

Absar Ahmad

Shrinking Log or Data File should be avoided. Please read the following
article for a comprhensive article about this.

http://www.karaszi.com/SQLServer/info_dont_shrink.asp

Show quote

"DC" wrote:

> Hi,
>
> I am using a database with massive update and insert action and
> therefore shrink logfiles every 15 minutes since the logs explode
> otherwise. Shrinking the logs results in a massive performance hit and
> usually takes about three minutes with huge disk queues.
>
> Is there any way to shrink the logs with lesser queues?
>
> TIA for any idea,
>
> Regards
> DC
>
>

27 Jan 2006 9:10 AM

DC

Thank you for the pointers. I did not find a good alternative to dbcc
shrinkfile in my situation though. I need to shrink if I want or not,
the log file is just growing too big if I don't shrink.

Regards
DC

26 Jan 2006 5:18 PM

Andrew J. Kelly

How about doing log backups instead so the logs don't grow so much. Or set
the db to SIMPLE recovery mode if you don't care about loosing data.

--
Andrew J. Kelly SQL MVP

Show quote

"DC" <d*@upsize.de> wrote in message
news:1138291176.284923.118980@g43g2000cwa.googlegroups.com...
> Hi,
>
> I am using a database with massive update and insert action and
> therefore shrink logfiles every 15 minutes since the logs explode
> otherwise. Shrinking the logs results in a massive performance hit and
> usually takes about three minutes with huge disk queues.
>
> Is there any way to shrink the logs with lesser queues?
>
> TIA for any idea,
>
> Regards
> DC
>

27 Jan 2006 9:06 AM

DC

The recovery mode already is simple. BACKUP LOG WITH TRUNCATE_ONLY
seems to do the same as dbcc shrinkfile, same performance hit due to
massive disk queueing.

Regards
DC