Transaction Log Too large

[Agnes]

Recently , I find that there is timeout occur when runing 'select .
statement'
Some said the Transaction Log too large will make SQL become slowly

Now, the transaction log is 14407M , is it too large ? Can I delete it ? (Do
I need to do backup first ?)

[zacks]

On Apr 20, 11:14 am, "Agnes" <[e-mail]:

Recently , I find that there is timeout occur when runing 'select .
statement'
Some said the Transaction Log too large will make SQL become slowly

Now, the transaction log is 14407M , is it too large ? Can I delete it ? (Do
I need to do backup first ?)

You would have better luck posting this question in a SQL group. But I
am familiar with SQL and I know that you cannot delete the transaction
log but there are various methods from shrinking it.

[Parag Joshi]

HI Agnes
You need to schedule regular transaction log backups which will
automatically truncate the log and archive the old one to a directory of
your choice. This should be coupled with a database backup at regular
intervals so that you dont have a long restore process if something goes
wrong. Create a database maintenance plan and configure it.
Check out microsoft articles on creating a database maintenance plan.
Regards
Parag

<za***@construction-imaging.comwrote in message
news:11**********************@o5g2000hsb.googlegro ups.com...

On Apr 20, 11:14 am, "Agnes" <[e-mail]:

>Recently , I find that there is timeout occur when runing 'select .
statement'
Some said the Transaction Log too large will make SQL become slowly

Now, the transaction log is 14407M , is it too large ? Can I delete it ?
(Do
I need to do backup first ?)

You would have better luck posting this question in a SQL group. But I
am familiar with SQL and I know that you cannot delete the transaction
log but there are various methods from shrinking it.