Site sponsored by: Idera Try Idera’s new SQL admin toolset
SQL Server Performance

  • Home
  • Articles
  • Forums
  • Tips
  • Quiz
  • FAQ's
  • Blogs
  • Software
  • Books
  • About Us
RSS Feeds
Sign in | Join


FAQ Topics

All FAQ's
General DBA
General Developer
DBA Performance Tuning
Developer Performance Tuning
Clustering
Error Messages

Write for Us

Share you SQL Server knowledge with others and raise your profile in the community More...
Latest Articles

Capture DDL Changes using Change Data Capture with SQL Server 2008 ...
Business Intelligence in Collaborative Planning, Forecasting and Replenishment
Inside SQL Server Cluster Setup and Troubleshooting Techniques - Part I ...
Configure and Manage Policy Based Management in SQL Server 2008 ...

More     
 
Latest FAQ's

Cannot Start SQL Server Service
Users are able to connect to report manager but not able ...
Errors when SQL Server Snapshot Replication is Running
How to Display Server Name or IP Address in a Reporting ...

More     
   
Latest Software Reviews

Spotlight on ApexSQL Doc 2008
ApexSQL Enforce
Embarcadero Change Manager
SQL Server DBA Dashboard

More     

Does SQL Server support table partitioning?



Question

I have a table with over 40 million rows.  I would like to partition the table base on the creation date.  Does SQL Server support table partitioning?

 

Answer

Even with the fastest hardware and optimally-written queries, there comes a point in the size of a table where there are just too many rows to handle quickly. In this user's case, it looks like 40 million rows is that point. For you, it might be more or less, depending on your situation.

Fortunately, in SQL Server 2000 and 2005, there is what is called "partitioned views." Essentially, what a partitioned view does is to allow you to divide your data into multiple tables (instead of one very large table), and to place these tables one one or more SQL Servers. What a partitioned view does is to join the data in all of the tables so that it appears that there is only a single table.

For example, you might divide a large table by year, or month (and year), or using some method that makes logical sense. This way, each table will be much more manageable. These multiple tables might be located on a single physical SQL Server (local partitioned view), or on multiple SQL Servers (distributed partitioned view). A distributed partitioned view is implemented on what is called a SQL Server federation of servers.

Both options allow you to more easily manage data and can contribute to faster performance.








Home | Peformance Articles | Audit Articles | Business Intelligence Articles | Clustering Articles | Developer Articles | Reporting Services Articles | DBA Articles | ASP.NET / ADO.NET Articles | DBA FAQ's | Developer Peformance FAQ's | DBA Peformance FAQ's | Developer FAQ's | Clustering FAQ's | Error Messages | Audit Tool Reviews | Backup Tool Reviews | Coding Tool Reviews | Compare Tool Reviews | Documentation Tool Reviews | Design Tool Reviews | Monitoring Tool Reviews | Log Tool Reviews | Reporting Tool Reviews | Clustering Tool Reviews | Security Tool Reviews | Change Management Tool Reviews | Remote Access Tool Reviews | Book Reviews | Security Tool Reviews | QDPMA Performance Tuning | ADO.NET / ASP.NET | Administration | Analysis/OLAP Services | Application Development | Configuration | Components | ETL | Hardware | High Availability | Hints | Index | Misc | Operating Systems | Performance Tuning | Replication | T-SQL | Views


              © 1999-2008 by T10 Media. All rights reserved