Click here to Skip to main content
15,170,651 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Hi All,
I am developing one project it should contains very large tables like millon of data is inserted daily.We have to maintain 6 months of the data.Performance issue is genearted in report for this how to handle data in sql server table.Can you please let u have any idea..
Posted
Comments
Christian Graus 27-Dec-13 15:15pm
   
Just to add, all your answers were links found with google. When your question is this vague, articles and not forum replies are where you'll find what you need.

Use Partitioned Tables and Indexes[^].

Partitioning large tables or indexes can have the following manageability and performance benefits.

•You can transfer or access subsets of data quickly and efficiently, while maintaining the integrity of a data collection. For example, an operation such as loading data from an OLTP to an OLAP system takes only seconds, instead of the minutes and hours the operation takes when the data is not partitioned.

•You can perform maintenance operations on one or more partitions more quickly. The operations are more efficient because they target only these data subsets, instead of the whole table. For example, you can choose to compress data in one or more partitions or rebuild one or more partitions of an index.

•You may improve query performance, based on the types of queries you frequently run and on your hardware configuration. For example, the query optimizer can process equi-join queries between two or more partitioned tables faster when the partitioning columns in the tables are the same, because the partitions themselves can be joined.
   

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)




CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900