A couple of years ago, we got in a panic where a transaction log had filled
up the hard drive. In order to get the server back up immediately (no time
for backup/shrink) we simply added an additional transaction log onto another
drive, then took care of the situation correctly.

I am DYING to get rid of this extra log file, but there seems to be no way
to do so. I can't delete it because it is not empty, yet I find no way to
tell SQL server to stop using it so I can clean it out and remove it.

Is this possible in any way, or am I stuck with this extra log file forever???
--
--Zorpie

Have a look at ALTER DATABASE and the EMPTY FILE option.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Zorpiedoman" <nowheremane@beatles.com> wrote in message
news:737180FE-AFC8-42CD-B59F-3522EBE326C2@microsoft.com...
>A couple of years ago, we got in a panic where a transaction log had filled
> up the hard drive. In order to get the server back up immediately (no
> time
> for backup/shrink) we simply added an additional transaction log onto
> another
> drive, then took care of the situation correctly.
>
> I am DYING to get rid of this extra log file, but there seems to be no way
> to do so. I can't delete it because it is not empty, yet I find no way to
> tell SQL server to stop using it so I can clean it out and remove it.
>
> Is this possible in any way, or am I stuck with this extra log file
> forever???
> --
> --Zorpie

I believe Andrew would say DBCC SHRINKFILE's EMPTYFILE.

You may have more info about this command from the following link:
http://msdn2.microsoft.com/en-us/library/ms189493.aspx

--
Ekrem Önsoy


"Zorpiedoman" <nowheremane@beatles.com> wrote in message
news:737180FE-AFC8-42CD-B59F-3522EBE326C2@microsoft.com...
>A couple of years ago, we got in a panic where a transaction log had filled
> up the hard drive. In order to get the server back up immediately (no
> time
> for backup/shrink) we simply added an additional transaction log onto
> another
> drive, then took care of the situation correctly.
>
> I am DYING to get rid of this extra log file, but there seems to be no way
> to do so. I can't delete it because it is not empty, yet I find no way to
> tell SQL server to stop using it so I can clean it out and remove it.
>
> Is this possible in any way, or am I stuck with this extra log file
> forever???
> --
> --Zorpie

Thanks for correcting me Ekrem. You are correct, my head was in the clouds.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Ekrem Önsoy" <ekrem@btegitim.com> wrote in message
news:5C9501C7-BE21-404A-AF5F-00B19E5EB09A@microsoft.com...
>I believe Andrew would say DBCC SHRINKFILE's EMPTYFILE.
>
> You may have more info about this command from the following link:
> http://msdn2.microsoft.com/en-us/library/ms189493.aspx
>
> --
> Ekrem Önsoy
>
>
> "Zorpiedoman" <nowheremane@beatles.com> wrote in message
> news:737180FE-AFC8-42CD-B59F-3522EBE326C2@microsoft.com...
>>A couple of years ago, we got in a panic where a transaction log had
>>filled
>> up the hard drive. In order to get the server back up immediately (no
>> time
>> for backup/shrink) we simply added an additional transaction log onto
>> another
>> drive, then took care of the situation correctly.
>>
>> I am DYING to get rid of this extra log file, but there seems to be no
>> way
>> to do so. I can't delete it because it is not empty, yet I find no way
>> to
>> tell SQL server to stop using it so I can clean it out and remove it.
>>
>> Is this possible in any way, or am I stuck with this extra log file
>> forever???
>> --
>> --Zorpie
>

It happens sometimes mate...

--
Ekrem Önsoy


"Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message
news:Ox1H9c3BIHA.5980@TK2MSFTNGP04.phx.gbl...
> Thanks for correcting me Ekrem. You are correct, my head was in the
> clouds.
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
>
> "Ekrem Önsoy" <ekrem@btegitim.com> wrote in message
> news:5C9501C7-BE21-404A-AF5F-00B19E5EB09A@microsoft.com...
>>I believe Andrew would say DBCC SHRINKFILE's EMPTYFILE.
>>
>> You may have more info about this command from the following link:
>> http://msdn2.microsoft.com/en-us/library/ms189493.aspx
>>
>> --
>> Ekrem Önsoy
>>
>>
>> "Zorpiedoman" <nowheremane@beatles.com> wrote in message
>> news:737180FE-AFC8-42CD-B59F-3522EBE326C2@microsoft.com...
>>>A couple of years ago, we got in a panic where a transaction log had
>>>filled
>>> up the hard drive. In order to get the server back up immediately (no
>>> time
>>> for backup/shrink) we simply added an additional transaction log onto
>>> another
>>> drive, then took care of the situation correctly.
>>>
>>> I am DYING to get rid of this extra log file, but there seems to be no
>>> way
>>> to do so. I can't delete it because it is not empty, yet I find no way
>>> to
>>> tell SQL server to stop using it so I can clean it out and remove it.
>>>
>>> Is this possible in any way, or am I stuck with this extra log file
>>> forever???
>>> --
>>> --Zorpie
>>
>