April 17, 2012 at 1:40 am
I'm working on performance issues of some tables with huge number of orders. I have these questions in my mind...
- can I write a partition function that splits tables in to two part: last month's orders and older ones ?
- if possible, somehow, should I use it concerning performance issues ?
and this is a question regarding of how do you do it:
lets say I partitioned this table in yearly basis. obviously files needed by partitioning functions calculated by highest value in table. lets say its April 2012. minimum value is January 2008. after partitioning I would have 5 files for years: 2008-2009-2010-2011-2012
my question if what will happen in 2013 ? should programmer have to manually append new filegroup and modify partitioning ? in this way, programmer must always be in contact with customer. is there any automatic way to create new filegroup at the end of every year ? or do you create extra file groups, lets say for 2013,2014,2015 and leave it ?
thanks...
April 17, 2012 at 3:10 am
You can certainly automate it. Just search for sliding window partitioning in google and you'll get an idea to automate it.
Online Trainer For SQL DBA and Developer @RedBushTechnologies with 18 yrs exp.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply