When do you need data partitioning? The data you see in relational database may need such a strategy if the volume is huge, for instance the data to store event-log information having the schema such as: [Id] INT (make this primary key clustered), [Unit_Id] UNIQUEIDENTIFIER, [EventType_Id] UNIQUEIDENTIFIER...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
03-12-2008
Filed under: sql server, performance, indexes, data, backup, bi, database, statistics, partition, monitoring, strategy, data warehouse
If you have a huge number of partitioned tables and indexes then the following query would help you to identify the list of objects that are involved. USE <database_name>; GO SELECT SCHEMA_NAME(o.schema_id) AS schema_name ,OBJECT_NAME(p.object_id) AS table_name ,i.name AS index_name ,p.partition_number...