August 18, 2009 at 9:59 am
I have a software company installing their software and database. The way they partitioned the database, they put the data in D drive and transaction log in H driver and that is fine. However they partitioned the drive to 1 G and they created the transaction log file to 1 G. They said they wanted to pre-extand the max size they anticipated and additional space on the drive was not needed.
Is this a good practice?
Thanks
August 18, 2009 at 10:01 am
Yep our SAP folk have done exactly that too, when i questioned they said that is sized as expected and doesnt need altering and wont need to have auto increase.
Oraculum
August 18, 2009 at 10:24 am
Loner (8/18/2009)
I have a software company installing their software and database. The way they partitioned the database, they put the data in D drive and transaction log in H driver and that is fine. However they partitioned the drive to 1 G and they created the transaction log file to 1 G. They said they wanted to pre-extand the max size they anticipated and additional space on the drive was not needed.Is this a good practice?
Thanks
A lot depends on what will be done with the database. If you need to re-index a table larger than 1 GB, that is not going to work very well. However, there is nothing to stop you from just adding another transaction log file on the other drive if it becomes necessary.
If both partitions are located on the same physical array, then it probably would have been better to just use one large partition.
August 18, 2009 at 12:43 pm
It's good practice if that is the largest the transaction log will ever need to be. 1GB is pretty small for a transaction log, unless it's a relatively small and/or infrequently used database.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply