|
|
Posted by Antar on 09/06/05 13:29
Hello,
I have a huge database (2 GB / month) and after a while it is becoming
non-operational (time-outs, etc.) So I have written an SQL sentence
(delete) that can reduce around 60% of the db size without compromising
the application data needs. The problem is that when I execute it, the
db does reduce its size 60%, but the transaction log increases at the
same rate. Can I execute the sentence in a "commit" or
"transaction" mode so to impede the SQL Server write in the log?
Thanks for the help!
Antonio
Navigation:
[Reply to this message]
|