We are updating the Partition function to use the new filegroup for data 2009 and after.<\/li>\n<\/ul>\nALTER TABLE dbo.PartitionOrnek SWITCH PARTITION 1 TO dbo.PartitionArchiveExample\r\n\r\nALTER PARTITION FUNCTION [RecordTimePartition]()\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 MERGE RANGE ('2007-01-01')\r\n\r\nALTER PARTITION SCHEME [RecordTimeScheme ]\r\nNEXT USED [FileGroup4]\r\nGO\r\nALTER PARTITION FUNCTION [RecordTimePartition]()\r\nSPLIT RANGE ('2009-01-01')<\/pre>\n <\/p>\n
TRANSFER ARCHIVED PARTITIONS TO ANOTHER DATABASE<\/h3>\n
To prevent the database from growing too large, I recommend that you move the archieve table to another database with the following script after this operation.<\/p>\n
BEGIN TRANSACTION\r\nINSERT INTO TestArchieveDB.dbo.PartitionArchiveExample\r\nSELECT * FROM Test.dbo.PartitionArchiveExample\r\nTRUNCATE TABLE Test.dbo.PartitionArchiveExample\r\nCOMMIT TRANSACTION<\/pre>\n <\/p>\n
You can also create a stored procedure and automate the operations we have done above.<\/p>\n
You should test all these operations before applying production.<\/p>\n\n
<\/div>\n