|
|
Posted by Erland Sommarskog on 11/05/05 16:37
helmut woess (hw@iis.at) writes:
> In this special case i would think about using a table per week. There is
> no faster way then DROP/CREATE or maybe TRUNCATE. You have to change a lot
> in the way you work with this data, but you have UNION and maybe you can
> use VIEWS.
> Or you use a big Solid State Disk for your database :-))
Since one table per week becomes quite a job to manage, I would go for
one table per month, and then truncate once per month.
If this would be too much data, I would then try every tenth day. This
makes it a lot easier to set up the check constraints for the partitions.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
Navigation:
[Reply to this message]
|