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