Tag Info

New answers tagged

1

Partitioning allows concurrent reorgs by partition, if all of your indexes are partitioned. If not, the partitions are still much smaller and use less workspace to reorg. And, internally, any "good" DBMS can do things in parallel with partitioned tables. That likely does NOT include MySQL or MyISAM, tho....


4

Rather than looking at index utilization, I'd look at the plan cache to find your queries with the highest amounts of logical reads. Usually when I'm dealing with partitioning, I find just a handful of queries that are dominating reads - like 50-80% of the servers' reads overall. Check those queries to see if they're successfully doing partition elimination. ...


0

Partitions have in their syntax the option to have different engines for every partition, but this is not (yet?) supported. Having different character sets for different partitions, however, may not make sense as all of them should have a common data structure. It is also not supported. Please understand that the charset is a property of a field, not of a ...


3

When you are working with partition switching, SQL Server will need to verify that the source table/partition boundaries can fit in the destination table/partition boundaries. In other words, you're trying to switch data from dbo.temp_table to dbo.play_table's partition 2. Think of it like this, the data for the c1 in dbo.temp_table is constrained only by ...


6

You can use sys.dm_db_index_physical_stats to identify the size of your partitions and how much space is being used. Use the page_count field to see the size of your partition. If you perform a SAMPLED or DETAILED scan, you will also get a value for avg_page_space_used_in_percent, which will allow you to estimate how much of the space in the partition is ...



Top 50 recent answers are included