The database that I just started to work with has a simple recovery model.
98 gigs. I can not figure out how the transaction log became so large. There
has never been a backup taken of the transaction log. How can the transaction
"Mike Epprecht (SQL MVP)" wrote:
> Hi
>
> Look at
http://msdn.microsoft.com/library/en-us/adminsql/ad_bkprst_565v.asp >
> If I were you, I would not back the log up, but rather set the recovery mode
> the Simple so it gets truncated.
> Then do your shrinks.
> Set the DB back the Full recovery
> Then a full DB backup
> Regularly schedule a transaction log backup using the DB Maintenance Plan
> Wizard.
>
> The T-SQL would be
> BACKUP LOG <dbname>
> TO DISK="drive:\path\filename.ext"
>
> See SQL Server Books Online for more Information.
>
> --
> --------------------------------
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
>
> IM: mike@epprecht.net
>
> MVP Program:
http://www.microsoft.com/mvp >
> Blog:
http://www.msmvps.com/epprecht/ >
> "Wendy Elizabeth" <WendyElizabeth@discussions.microsoft.com> wrote in
> message news:C2A1BE29-87E9-4945-A182-F4D19982E758@microsoft.com...
> >I am relatively new to sql server 2000. I have a transaction log that is 98
> > gigs in size that has never been backed up. This transaction log file is
> > too
> > big and needs to be decreased in size.
> > Can you tell me how I would make my first full backup of this transaction
> > log file?
> >
> > To shrink the transaction log would i do something like:
> >
> > Use [sales]
> > Go
> > alter database [sales] set recovery simple
> > go
> > dbcc shrinkfile (sales_log, 100)
> > go
> > checkpoint
> > go
> > dbcc shrinkfile (sales_log, 100)
> > alter database [sales] set recovery full
> > go
> >
> > Then how would I do the full backup of the transaction log again?
> >
> > Let me know.
> >
> > Thanks!
> >
>
>
