Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-09-19 : 09:31:31
|
| JerryB writes "We've recently updated from SQL 7 to SQL2K SP2. We drop and recreate indexes, nightly as part of our maintenance plan. The log sizes in 7.0 were around 90mb. The same logs in Sql2K are roughly 2.8gb (same size as the database). In Sql2K we are using the FULL recovery model for point-in-time restore ability. The maint plans on 7.0 and 2000 are setup to run optimizations before the backups. The optimizations rebuild the indexes which is the cause of the log size increase. The reindex seemed to be minimally logged in 7.0 but fully logged in 2000. Does anyone know what was changed in SQL2K that would cause this log size increase? I do not want to swtich to the Bulk-Logged recovery option and lose point-in-time restore ability. Any suggestions would be appreciated. " |
|
|
davy_boy2000
Starting Member
28 Posts |
Posted - 2002-09-20 : 09:12:18
|
| The indexes aren't padded out with fill factors are they? |
 |
|
|
|
|
|
Transaction logs in Sql 2000 larger than 7.0