|
|
Posted by Trevor Best on 05/21/07 14:05
On May 21, 12:36 pm, "Greg D. Moore \(Strider\)"
<mooregr_deletet...@greenms.com> wrote:
> "Trevor Best" <googlegro...@besty.org.uk> wrote in message
>
> news:1179743114.957187.301860@b40g2000prd.googlegroups.com...
>
> >I have a client with 150MB database, the transaction log file is
> > nearly 23GB. It's a PITA for me to backup his data and restore it on
> > my server as it takes about 30 minutes to restore as it re-creates a
> > 23GB file with no transactions in it :-\
>
> Why is it that large?
I think it has 18 months worth of transactions in it. (I'm not their
dba :-)
> I'd find out first why it's a 23GB transaction log file. If it's a fluke,
> then yes, a single shrink to a more reasonable size is probably ok. My guess
> is at some point they simply were NOT doing transaction log backups and as a
> result it just kept growing. So they either instituted transaction log
> backups (good) or put the database into "SIMPLE" recovery mode (potentially
> bad) and just left the log file the size it was.
I did set up backup of db and logs and maintenance plans on their
server when it first installed (Aug 05), I just checked and Agent
isn't running so I guess he normal maintenance plan hasn't run. I hope
they backup the database some other way :-\ Thanks for your comments.
Navigation:
[Reply to this message]
|