You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-functions/durable/quickstart-mssql.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,18 +16,18 @@ Durable Functions supports several [storage providers](durable-functions-storage
16
16
17
17
## Note on data migration
18
18
19
-
Migration of [Task Hub data](durable-functions-task-hubs.md) across storage providers isn't currently supported. Function apps with existing runtime data will start with a fresh, empty task hub after switching to the MSSQL backend. Similarly, the task hub contents created with MSSQL cannot be preserved when switching to a different storage provider.
19
+
Migration of [Task Hub data](durable-functions-task-hubs.md) across storage providers isn't currently supported. Function apps with existing runtime data will start with a fresh, empty task hub after switching to the MSSQL backend. Similarly, the task hub contents created with MSSQL can't be preserved when switching to a different storage provider.
20
20
21
21
## Prerequisites
22
22
23
-
The following steps assume that you are starting with an existing Durable Functions app and are familiar with how to operate it.
23
+
The following steps assume that you're starting with an existing Durable Functions app and are familiar with how to operate it.
24
24
25
25
In particular, this quickstart assumes that you have already:
26
26
1. Created an Azure Functions project on your local machine.
27
27
2. Added Durable Functions to your project with an [orchestrator function](durable-functions-bindings.md#orchestration-trigger) and a [client function](durable-functions-bindings.md#orchestration-client) that triggers it.
28
28
3. Configured the project for local debugging.
29
29
30
-
If this is not the case, we suggest you start with one of the following articles, which provides detailed instructions on how to achieve all the requirements above:
30
+
If this isn't the case, we suggest you start with one of the following articles, which provides detailed instructions on how to achieve all the requirements above:
31
31
32
32
-[Create your first durable function - C#](durable-functions-create-first-csharp.md)
33
33
-[Create your first durable function - JavaScript](quickstart-js-vscode.md)
@@ -42,7 +42,7 @@ If this is not the case, we suggest you start with one of the following articles
42
42
43
43
You'll need to install the latest version of the MSSQL storage provider Extension on NuGet. This usually means to include a reference to it in your `.csproj` file and building the project.
44
44
45
-
The Extension package to install depends on the .NET worker you are using:
45
+
The Extension package to install depends on the .NET worker you're using:
46
46
- For the _in-process_ .NET worker, install [`Microsoft.DurableTask.SqlServer.AzureFunctions`](https://www.nuget.org/packages/Microsoft.DurableTask.SqlServer.AzureFunctions).
47
47
- For the _isolated_ .NET worker, install [`Microsoft.Azure.Functions.Worker.Extensions.DurableTask.SqlServer`](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.DurableTask.SqlServer).
48
48
@@ -148,7 +148,7 @@ Below is an example `local.settings.json` assigning the default Docker-based SQL
148
148
149
149
### Update host.json
150
150
151
-
Edit the storage provider section of the `host.json` file so it sets the `type` to `mssql`. We'll also specify the connection string variable name, `SQLDB_Connection`, under `connectionStringName`. We'll set `createDatabaseIfNotExists` to `true`; this setting creates a database named `DurableDB` if one does not already exists, with collation `Latin1_General_100_BIN2_UTF8`.
151
+
Edit the storage provider section of the `host.json` file so it sets the `type` to `mssql`. We'll also specify the connection string variable name, `SQLDB_Connection`, under `connectionStringName`. We'll set `createDatabaseIfNotExists` to `true`; this setting creates a database named `DurableDB` if one doesn't already exists, with collation `Latin1_General_100_BIN2_UTF8`.
0 commit comments