Hello everybody,
I could get any problem if i set recovery model to simple?
My database uses only full backup?
I dont need to do differential or incremental backup.
I dont have problems with backup size.
I have problems to keep the log file short.
Thanks
I would like more explanation about that.
Leandro L S
Vitoria-ES
BRAZILLog files are log files .. they grow!
If you have limited space, simply restrict their size.
"Leandro Loureiro dos Santos" <naofalo@.com.vc> wrote in message
news:OLJ8XfdGEHA.3096@.TK2MSFTNGP11.phx.gbl...
> Hello everybody,
> I could get any problem if i set recovery model to simple?
> My database uses only full backup?
> I dont need to do differential or incremental backup.
> I dont have problems with backup size.
> I have problems to keep the log file short.
> Thanks
> I would like more explanation about that.
> Leandro L S
> Vitoria-ES
> BRAZIL
>|||Hi,
Log files grow based on your type of transactions, if you have bulk
transaction worth 1 GB, automatically transaction log file will grow to a
higher size and the log file will be cleared after the commit (Since u are
using SIPLE recovery). But the physical file size wont reduce.
How to control the growth
1. Insted of doing the bulk transaction do it in batches, so there will be
commit inbetween , this will ensure that file will not grow bigger.
How to reduce the file size
Execute the below commands in Query Analyzer;
1. Backup log <database_name> with no_log
2. use <dbname>
go
dbcc shrinkfile('logical_logfilename','trunca
teonly')
Thanks
Hari
MCDBA
"Leandro Loureiro dos Santos" <naofalo@.com.vc> wrote in message
news:OLJ8XfdGEHA.3096@.TK2MSFTNGP11.phx.gbl...
> Hello everybody,
> I could get any problem if i set recovery model to simple?
> My database uses only full backup?
> I dont need to do differential or incremental backup.
> I dont have problems with backup size.
> I have problems to keep the log file short.
> Thanks
> I would like more explanation about that.
> Leandro L S
> Vitoria-ES
> BRAZIL
>|||In the SIMPLE recovery model, your log file needs to be large enough to
accommodate your largest single transaction. Some transactions, such as
DBCC DBREINDEX on a large table, can perform a lot of logging and your log
needs to be sized accordingly.
Hope this helps.
Dan Guzman
SQL Server MVP
"Leandro Loureiro dos Santos" <naofalo@.com.vc> wrote in message
news:OLJ8XfdGEHA.3096@.TK2MSFTNGP11.phx.gbl...
> Hello everybody,
> I could get any problem if i set recovery model to simple?
> My database uses only full backup?
> I dont need to do differential or incremental backup.
> I dont have problems with backup size.
> I have problems to keep the log file short.
> Thanks
> I would like more explanation about that.
> Leandro L S
> Vitoria-ES
> BRAZIL
>
No comments:
Post a Comment