![]() ![]() You also don't have to worry about deleting a logical partition when the underlying rows belonging to that partition is deleted.įor all elastic tables, the partitionid column should: There's no limit on the number of logical partitions you can have in a table. Groups of items that have specific values for product category, such as Clothing, Books, Electronic Appliances and Pet supplies, form distinct logical partitions.ĭataverse transparently and automatically manages logical partitions associated with a table. For example, in a table that contains data about various products, you can use product category as the partitionid for the table. A logical partition in an elastic table consists of a set of rows that have the same partitionid. The partitionid value you should use depends on the nature of your data. It is important to understand that unique references for elastic tables is the combination of the primary key AND the partitionid value. In other words, you can create multiple records with the same primary key, but different partitionid values. When you use a custom partitionid value, the primary key value doesn't have a unique constraint. If you don't set a partitionid value for each row, the value will remain null and you will not be able to change it later. To get the optimum performance available with elastic tables, you must choose and consistently apply a partitioning strategy. All elastic tables contain a system-defined Partition Id string column with the schema name PartitionId and logical name partitionid.Īzure Cosmos DB ensures that the rows in a table are divided into distinct subsets called logical partitions that are formed based on the value of the partitionid column of each row. A combination of both types of tables may be appropriate.įor more information about differences in modeling elastic tables, see:Įlastic tables use Azure Cosmos DB partitioning to scale individual tables to meet the performance needs of your application. The choice of table should be based on the specific needs of your application. Your application requires complex joins.Your application requires relational modeling and needs transactional capability across tables or during plugin execution.Your application requires strong data consistency.You need to handle a high volume of read and write requests.You need horizontal scaling to handle workload growth over time or bursty workload at a given point.Your data may be unstructured or semi-structured, or if your data model may constantly be changing.Whether you should use an elastic table depends on the specific needs of your data and your application. These features are available before an official release so that customers can get early access and provide feedback. Preview features aren’t meant for production use and may have restricted functionality. ![]()
0 Comments
Leave a Reply. |