Backup to NULL

Hi,
I have a database that was left with recovery set to full and receving a lot
of updates. Log file has become huge but there were no transaction log
backups being done. Until I needed to trim the transaction log file now
being 25 GB (data file is only 1.5GB) because there is no more space in the
drive.
To be able to shrink it I plan to back it up first, then change the recovery
from full to simple and then shrink the log file. My problem is I don't hav
e
any more disk space to hold the transaction log backup. Is there a way to
just backup the 20GB+ transaction log to the great void? Null? or wherever?
Please share me your insights, comments and suggestion are welcome.
TIA.
CarloVino
--
...You can specify WITH TRUNCATE_ONLY on the BACKUP LOG command so that
committed data are removed from the log without creating a backup file.
Then shrink the log file to the desired size.
Afterwards, backup the database and schedule regular transaction log backups
to keep your log size reasonable.
Hope this helps.
Dan Guzman
SQL Server MVP
"CarloVino" <CarloVino@.discussions.microsoft.com> wrote in message
news:06741C7C-D44A-4D7E-B65B-8F2E8C23B7B1@.microsoft.com...
> Hi,
> I have a database that was left with recovery set to full and receving a
> lot
> of updates. Log file has become huge but there were no transaction log
> backups being done. Until I needed to trim the transaction log file now
> being 25 GB (data file is only 1.5GB) because there is no more space in
> the
> drive.
> To be able to shrink it I plan to back it up first, then change the
> recovery
> from full to simple and then shrink the log file. My problem is I don't
> have
> any more disk space to hold the transaction log backup. Is there a way to
> just backup the 20GB+ transaction log to the great void? Null? or
> wherever?
> Please share me your insights, comments and suggestion are welcome.
> TIA.
> CarloVino
> --
> ...|||BACKUP LOG MyDatabase with TRUNCATE_ONLY. Look it up in BOL.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"CarloVino" <CarloVino@.discussions.microsoft.com> wrote in message
news:06741C7C-D44A-4D7E-B65B-8F2E8C23B7B1@.microsoft.com...
> Hi,
> I have a database that was left with recovery set to full and receving a
> lot
> of updates. Log file has become huge but there were no transaction log
> backups being done. Until I needed to trim the transaction log file now
> being 25 GB (data file is only 1.5GB) because there is no more space in
> the
> drive.
> To be able to shrink it I plan to back it up first, then change the
> recovery
> from full to simple and then shrink the log file. My problem is I don't
> have
> any more disk space to hold the transaction log backup. Is there a way to
> just backup the 20GB+ transaction log to the great void? Null? or
> wherever?
> Please share me your insights, comments and suggestion are welcome.
> TIA.
> CarloVino
> --
> ...