|
|
|
SSC-Enthusiastic
 
Group: General Forum Members
Last Login: Wednesday, June 24, 2009 4:53 AM
Points: 118,
Visits: 53
|
|
I have a big database (400 GB) with a big table (120GB).
In a development server, I partitioned the big table into 5 partitions (5 filegroups, 1 file per filegroup), and I left intentionally a significant part to simulate the periodical maintenance process of splitting.
The recovery model is set to simple, to minimize the log growth.
Then, I split the remaining data rows into a new created file/filegroup.
I have finally 6 partitions, balanced in size by number of rows.
The result is correct, but the transaction log grows until 220 GB, even with the simple recovery model.
¿What is happening?
Thanks in advance.
|
|
|
|
|
SSC-Enthusiastic
Group: General Forum Members
Last Login: Monday, June 29, 2009 6:57 PM
Points: 150,
Visits: 173
|
|
Design your partition table in such a manner that you always split a partition which contains no data. Same goes with Merge. Otherwise your split and merge operation will consume high IO and will result in big transaction log file.
For eg. lets say that i have to retain only 50 days worth of data.
Then i will create 52 partitions and the first and last will always be empty
|
|
|
|
