Hello,
I have a database with a transaction log file of 500MB. I want to increase it to 10000MB, but this must also become the new "minimum logsize".
According to BOL the ALTER DATABASE statement with the SIZE=10000MB property should do the trick... BUT after an autoshrink or forced shrink ( DBCC SHRINKDATABASE ) of the database the size is shrunk to below 10000MB. I do not want this to happen. ( It seems like a bug or incorrect description in BOL )
Creating a new transaction log is not possible because it is the primary transaction log. This file cannot be removed. Creating a new database with the same name, detaching the original database and retaching it with the newly created transaction log ( thus trying to fool sql server ) does also not work.
Any ideas anyone?
I have a database with a transaction log file of 500MB. I want to increase it to 10000MB, but this must also become the new "minimum logsize".
According to BOL the ALTER DATABASE statement with the SIZE=10000MB property should do the trick... BUT after an autoshrink or forced shrink ( DBCC SHRINKDATABASE ) of the database the size is shrunk to below 10000MB. I do not want this to happen. ( It seems like a bug or incorrect description in BOL )
Creating a new transaction log is not possible because it is the primary transaction log. This file cannot be removed. Creating a new database with the same name, detaching the original database and retaching it with the newly created transaction log ( thus trying to fool sql server ) does also not work.
Any ideas anyone?