Microsoft Dataverse Elastic Tables

Introduction

Elastic tables give the same familiar user experience and API as standard tables. Elastic tables have many of the same features and settings as standard tables and special features and capabilities made available by Azure Cosmos DB. Standard and Elastic tables use the Dataverse database capacity.

Elastic tables are designed to manage large volumes of data in real-time. Scalability, latency, and performance problems don’t arise when importing, storing, and analyzing large volumes of data with elastic tables. Elastic tables are special because they can be horizontally scaled, have flexible structures, and automatically remove data after a set duration of time. Tens of millions of rows may be automatically taken by elastic tables per hour. Background processes may collect IoT signals, estimate maintenance requirements, and schedule personnel ahead of time.

Elastic tables offer unlimited auto-scaling for storage capacity and throughput, or the quantity of data added, modified, or removed within a specified period, according to the application workload.

If the business requires a very large number of data writes, application makers can leverage Dataverse multiple request APIs, such as CreateMultiple, UpdateMultiple, and DeleteMultiple, to gain more throughput within Dataverse’s throttling limitations.

When should you consider using Dataverse elastic tables?

The type of table you choose should be decided by the unique requirements of your application. A combination of both tables may be useful.

Elastic tables should be used when:

• Your data may be unstructured or semi-structured, and your data model may be changing all the time.
• Automatic horizontal scaling is required.
• There are a lot of read-and-write requests that you must manage.

Standard tables should be used when

• Strong consistency is required for your application.
• Relational modeling is necessary for your application, as are transactional capabilities between tables and throughout the plugin execution phases.
• Complex joins are required for your application.

Elastic tables provide support.

• Create, retrieve, update, and delete (CRUD) actions include bulk deletion, requests from plug-ins, and numerous API activities (for high throughput).
• Relationships:
  • One-to-many
  • Many-to-one when the N table is standard.
• Dataverse search, mobile offline, auditing, change monitoring, and record ownership.
• File type property in a file column.

Support for security features

• either owned by the user or the organization.
• field-level security

Create an Elastic Table

1. Sign into Power Apps.
2. Select tables in the left pane.
3. Click on New Table and select Set Advanced Properties.

4. Give the name of the table and select the type a Elastic

5. And Click save.

6. the time to live column.

An elastic table automatically creates a time-to-live column. The time-period value in seconds can be added as needed. The data is automatically deleted after the set time frame.