Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
michaelfallas
Starting Member
1 Post |
 Posted - 2010-08-09 : 11:25:46
|
| Hi,I need to stored 5 years of information from now to 2015. I also need to store this information per month.Something like this:2010 January February .... December2011 January February .... DecemberAnd so on. But I don't want to create a database per year, because the maintenance goes complicated.How can I solve this problem using partitioned tables in SQL Server 2005 |
|
|
Lamprey
Master Smack Fu Yak Hacker
4614 Posts |
Posted - 2010-08-09 : 12:53:06
|
| I don't know the syntax off the top of my head, but do some searching for Partitioned Tables and play around with creating partitioned schemas and function and such.One thing to be aware of is what happens when you need to drop off old partitions. It might make sense in the way it was intended. In that, when you want to "archive" and old partition to slower disk or something that it'll move it there. But, in another sense, it can be confusing and very costly if you don't set your partitions up right because SQL will move all the data around and that might be unexpected. I know I was surprised by how it worked when I first messed with it. |
 |
|
|
|
|
|
Partitioned tables in SQL Server 2005