Hello
 Is there any time / way /procedure to delte the log file and let SQL
 recreate it without losing any data. In other words - at what point in time
 can one be safely assured that all data in the log file is committed to the
 database.
 reason - have 1.2gb database and 9gb logfile - caused by duplicating
 another database ( importing thru ODBC ) each night and would like to kill
 the log file each morning after the transfer - the SQL database is only
 used for reporting as the other package has lots of limitations - yep - we
 are working on converting it all to SQL so this replication doesn't have to
 happen but that is still a fair way off
 TIA
 PeteIf your recovery plan is to restore from your last full database backup (or
rerun your import), you can set the database recovery model to SIMPLE so
that committed transactions are automatically removed from the log.
You can run DBCC SHRINKFILE to release unused log space back to the OS. The
log will still need to be large enough to accommodate your largest
transaction so you probably don't want to do this routinely.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Pete" <p0911@.hotmail.com> wrote in message
news:eAMZK0PSEHA.1568@.TK2MSFTNGP11.phx.gbl...
> Hello
> Is there any time / way /procedure to delte the log file and let SQL
> recreate it without losing any data. In other words - at what point in
time
> can one be safely assured that all data in the log file is committed to
the
> database.
> reason - have 1.2gb database and 9gb logfile - caused by duplicating
> another database ( importing thru ODBC ) each night and would like to kill
> the log file each morning after the transfer - the SQL database is only
> used for reporting as the other package has lots of limitations - yep - we
> are working on converting it all to SQL so this replication doesn't have
to
> happen but that is still a fair way off
> TIA
> Pete
>sql
Subscribe to:
Post Comments (Atom)
 
No comments:
Post a Comment