SQL server

Dapr doesn’t transform state values while saving and retrieving states. Dapr requires all state store implementations to abide by a certain key format scheme (see the state management spec. You can directly interact with the underlying store to manipulate the state data, such as:

  • Querying states.
  • Creating aggregated views.

The easiest way to connect to your SQL Server instance is to use the:

Note

When you configure an Azure SQL database for Dapr, you need to specify the exact table name to use. The following Azure SQL samples assume you’ve already connected to the right database with a table named “states”.

The above query returns all rows with id containing “myapp||”, which is the prefix of the state keys.

To get the state data by a key “balance” for the application “myapp”, use the query:

Read the Data field of the returned row. To get the state version/ETag, use the command:

To get all the state keys associated with an actor with the instance ID “leroy” of actor type “cat” belonging to the application with ID “mypets”, use the command:

To get a specific actor state such as “food”, use the command:

    Warning

    You should not manually update or delete states in the store. All writes and delete operations should be done via the Dapr runtime. The only exception: it is often required to delete actor records in a state store, once you know that these are no longer in use, to prevent a build up of unused actor instances that may never be loaded again.