Note that the filter syntax used in the examples below is from the Table service REST API, for more information see Query Entities. These result in the following general guidelines for designing Table service queries. The article Azure Table storage overview describes some of the key features of the Azure Table service that have a direct influence on designing for query. The following examples assume the table service is storing employee entities with the following structure (most of the examples omit the Timestamp property for clarity): Column name How your choice of PartitionKey and RowKey impacts query performance Optimizing queries for the Table service.How your choice of PartitionKey and RowKey impacts query performance.The topics covered in this section include: This section focuses on the key issues you must address when you design your tables for querying. For example, in a relational database it's often possible to address performance issues simply by adding indexes to an existing database: this is not an option with the Table service. With the Table service, it's important to get the design correct up front because it's difficult and expensive to change it later.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |