|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Friday, June 12, 2009 8:16 AM
Points: 38,
Visits: 129
|
|
Thank you for your hints. I also think now that it is not good to shrink the transcation log to 1MB. Although the recovery mode is set to simple (so only the last transactions is stored in the transaction log), the growth of the transaction log is an expensive operation. But, why should the transaction log size set to 10% of the database size? Has someone experiences which is a good value in simple recovery mode?
Regards,
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Friday, February 22, 2013 1:27 AM
Points: 469,
Visits: 596
|
|
There are no definitive rules on how you should size the database log file. If I may bore you with my past, back in 1993 I was sent off to Sybase to learn about Sybase System 10. As we all know Sybase and SQL Server are one and the same (poetic licence now I feel) and back then Sybase were saying that, as a good starting point, the log file should be 20% of the size of the database or twice the size of the largest table on which you might perform a single update which hits every row.
But really it depends on how your database is used. One of the databases I look after has data files totalling 1.5TB but the log file is sized at 5GB which is roughly 3%.
Mike
|
|
|
|