patternsqlMinor
Suggestion required for Large Database Optimization and performance
Viewed 0 times
databaseoptimizationlargesuggestionforperformanceandrequired
Problem
We are creating a large database with estimated growth rate 200 million+ records per annum. The database is use for analysis purpose and we will generate different tabular and graphical reports from available data. we've some concerns and require technical input and advices.
Any suggestion for optimization and performance of database is also appreciated.
- What impact we may see in future for very large table? Is there any limitation on number of records in one table or size of table?
- What is the best way to index large data tables like this?
Any suggestion for optimization and performance of database is also appreciated.
Solution
SQL Server DENALI will have column store indexes but this won't come until the end of this year or early next year but from what I have seen so far (very little), it will definitely help.
In SQL Server partitioning is your best friend here. And to your question abt the limitation of # of rows in a table, it is limited only by storage space.
http://msdn.microsoft.com/en-us/library/ms143432(v=sql.100).aspx
As tables grow, adding and updating the data will take some time and you may want to look at using minimal logging if you are using SQL Server 2008.
http://sqlcat.com/whitepapers/archive/2009/02/15/the-data-loading-performance-guide-2008.aspx
And for large tables, updating indexes frequently can take significant times and have seen cases where updating the statistics will give you a quick boost instead of frequent index rebuilds.
In SQL Server partitioning is your best friend here. And to your question abt the limitation of # of rows in a table, it is limited only by storage space.
http://msdn.microsoft.com/en-us/library/ms143432(v=sql.100).aspx
As tables grow, adding and updating the data will take some time and you may want to look at using minimal logging if you are using SQL Server 2008.
http://sqlcat.com/whitepapers/archive/2009/02/15/the-data-loading-performance-guide-2008.aspx
And for large tables, updating indexes frequently can take significant times and have seen cases where updating the statistics will give you a quick boost instead of frequent index rebuilds.
Context
StackExchange Database Administrators Q#3088, answer score: 5
Revisions (0)
No revisions yet.