Partitioning

Learn about the benefits and drawbacks of using database partitioning (sharding) to help improve performance and maintenance tasks.

Learn how to take a very large SQL Server table and convert it to a partitioned view to help improve management and performance.

In this article we look at SQL Server table partitioning and why you would not want to create the maximum 15,000 partitions that are possible for a ta

In this article we cover how to setup partitioning for a SQL Server table and then how to partition a table that has a columnstore index.

In this we look at how we to quickly split up data from a SQL Server table into relatively equal size buckets.

In this tip we look at how to implement sliding window partitioning in SQL Server to quickly purge or archive old data.

SQL Server Database Administrators prefer TRUNCATE TABLE statement over the classic DELETE statement as it is faster, minimally logged and consume less server resources. Learn how to truncate only a portion of the table with partitions.

I have read many articles on SQL Server partitioning and how to create a partitioned table, but I have an existing SQL Server database that has a few very large tables that could benefit from partitioning. What are the steps required to partition an alrea

SQL Server Partitioning can be a bit confusing and can lead some companies in a different direction as far as archiving data. Writing the T-SQL code to create partition functions, partition schemes, and then altering the table to use the partition can be

Many companies now have a requirement to keep data for long periods of time. While this data does have to be available if requested, it usually does not need to be accessible by the application for any current transactions. Data that falls into this categ

I am using partitioning in my database. Is there an easy way for me to identify partitions that may have too much data so they can be split? Check out the examples and scripts in this tip to find out.

Partitioning, introduced with SQL Server 2005 is a godsend for working with very large tables. In this tip I will cover some data partitioning myths and truths you should know about.

Sales data in my production database has increased significantly. I am planning to archive this data apart from the production database, so this can still be used for reporting purposes. I am conscious about performance issues while inserting new data to

SQL Server Books Online (BOL) suggests that in order to clean up old partitions from a partition table, you should either issue a DELETE or SWITCH command. BOL also suggests that while SWITCHING partitions, you should set up a NON PARTITIONED TABLE in the

Learn how partitioning SQL Server data has query performance benefits.

One of the challenges of working with large datasets or datasets that become stale is the need to move large chunks of data in and out of your tables. This can be done with large INSERT and DELETE statements or by using views, but with SQL Server 2005 da

With the increasing use of SQL Server to handle all aspects of the organization as well as the increased use of storing more and more data in your databases there comes a time when tables get so large it is very difficult to perform maintenance tasks or t