I have just upgraded several databases from SQL Server 7 to SQL Server 2000. When I run my index job, my transaction log grows too much. When I ran the same job my 3.8 GB database needed a log size of about 1.0 GB. I never had a problem with it needing to be any bigger. Now when I run my index job my 3.8 GB database log file grows to 2.8 GB. I even have an alert that backups the transaction log if my log file gets to be 80% full. Can anyone tell me why in SQL 2000 this happens? I am setting my free space per page to 10%. Any Suggestions