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: azure-sql/database/automated-backups-overview.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -161,7 +161,10 @@ Hyperscale databases use a different backup scheduling mechanism. For more infor
161
161
162
162
Backups that are no longer needed to provide PITR functionality are automatically deleted. Because differential backups and log backups require an earlier full backup to be restorable, all three backup types are purged together in weekly sets.
163
163
164
-
For all databases, including [TDE-encrypted](transparent-data-encryption-tde-overview.md) databases, backups are compressed to reduce backup storage consumption and costs. Average backup compression ratio is 3 to 4 times. However, it can be significantly lower or higher depending on the nature of the data and whether data compression is used in the database.
164
+
For all databases, including [TDE-encrypted](../database/transparent-data-encryption-tde-overview.md) databases, all full and differential backups are compressed, to reduce backup storage compression and costs. Average backup compression ratio is 3 to 4 times. However, it can be significantly lower or higher depending on the nature of the data and whether data compression is used in the database.
165
+
166
+
> [!IMPORTANT]
167
+
> For TDE-encrypted databases, log backups files are not compressed for performance reasons. Log backups for non-TDE-encrypted databases are compressed.
165
168
166
169
Azure SQL Database computes your total used backup storage as a cumulative value. Every hour, this value is reported to the Azure billing pipeline. The pipeline is responsible for aggregating this hourly usage to calculate your consumption at the end of each month. After the database is deleted, consumption decreases as backups age out and are deleted. After all backups are deleted and PITR is no longer possible, billing stops.
Copy file name to clipboardExpand all lines: azure-sql/managed-instance/automated-backups-overview.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -154,7 +154,10 @@ In other words, for any point in time during the retention period, there must be
154
154
155
155
Backups that are no longer needed to provide PITR functionality are automatically deleted. Because differential backups and log backups require an earlier full backup to be restorable, all three backup types are purged together in weekly sets.
156
156
157
-
For all databases, including [TDE-encrypted](../database/transparent-data-encryption-tde-overview.md) databases, backups are compressed to reduce backup storage compression and costs. Average backup compression ratio is 3 to 4 times. However, it can be significantly lower or higher depending on the nature of the data and whether data compression is used in the database.
157
+
For all databases, including [TDE-encrypted](../database/transparent-data-encryption-tde-overview.md) databases, all full and differential backups are compressed, to reduce backup storage compression and costs. Average backup compression ratio is 3 to 4 times. However, it can be significantly lower or higher depending on the nature of the data and whether data compression is used in the database.
158
+
159
+
> [!IMPORTANT]
160
+
> For TDE-encrypted databases, log backups files are not compressed for performance reasons. Log backups for non-TDE-encrypted databases are compressed.
158
161
159
162
Azure SQL Managed Instance computes your total used backup storage as a cumulative value. Every hour, this value is reported to the Azure billing pipeline. The pipeline is responsible for aggregating this hourly usage to calculate your consumption at the end of each month. After the database is deleted, consumption decreases as backups age out and are deleted. After all backups are deleted and PITR is no longer possible, billing stops.
This example installs [!INCLUDE [sssql19-md](../includes/sssql19-md.md)] on RHEL 8.x. If you want to install a different version of [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)] or RHEL, change the Microsoft repository paths accordingly.
33
33
34
-
Save the sample script to a file and then to customize it. You'll need to replace the variable values in the script. You can also set any of the scripting variables as environment variables, as long as you remove them from the script file.
34
+
Save the sample script to a file. To customize it, you need to replace the variable values in the script. You can also set any of the scripting variables as environment variables, as long as you remove them from the script file.
35
35
36
36
> [!IMPORTANT]
37
37
> The `SA_PASSWORD` environment variable is deprecated. Use `MSSQL_SA_PASSWORD` instead.
This article describes the data that Azure Arc-enabled SQL Server transmits to Microsoft.
15
+
This article describes the data that Azure Arc-enabled [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] transmits to Microsoft. Azure Arc-enabled [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] collects usage data as described in this article and at [Monitor Azure Arc-enabled [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)]](sql-monitoring.md).
16
16
17
-
Azure Arc-enabled SQL Server, and any of the related Azure Arc-enabled services, don't store any customer data.
17
+
Azure Arc-enabled [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] does not collect any personally identifiable information (PII) or end-user identifiable information, or store any customer data.
18
18
19
19
## Related products
20
20
21
-
Azure Arc-enabled SQL Server uses the following products:
21
+
Azure Arc-enabled [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] uses the following products:
22
22
23
23
- Azure Arc-enabled servers
24
24
25
-
The following data is collected to Azure for Azure Arc-enabled SQL Servers:
26
-
27
25
## Azure Arc-enabled SQL Server
28
26
27
+
The following data is collected for Azure Arc-enabled [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] instances:
28
+
29
29
| Description | Property name | Property type |
30
30
| :-- | :-- | :-- |
31
31
| SQL Server edition |`Edition`|`string`|
32
32
| Resource ID of the hosting Azure Arc for Servers resource |`ContainerResourceId`|`string`|
33
33
| Time when the resource was created |`CreateTime`| string |
34
-
| The number of logical processors used by the SQL Server instance |`VCore`|`string`|
34
+
| The number of logical processors used by the [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] instance |`VCore`|`string`|
35
35
| Cloud connectivity status |`Status`|`string`|
36
36
| SQL Server update level |`PatchLevel`|`string`|
37
37
| SQL Server collation |`Collation`|`string`|
@@ -40,9 +40,9 @@ The following data is collected to Azure for Azure Arc-enabled SQL Servers:
40
40
| Dynamic TCP ports used by SQL Server |`TcpDynamicPorts`|`string`|
41
41
| Static TCP ports used by SQL Server |`TcpStaticPorts`|`string`|
42
42
| SQL Server product ID |`ProductId`|`string`|
43
-
|SQL Server provisioning state |`ProvisioningState`|`string`|
43
+
|[!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] provisioning state |`ProvisioningState`|`string`|
44
44
45
-
The following JSON document is an example of the SQL Server - Azure Arc resource.
45
+
The following JSON document is an example of the [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] - Azure Arc resource
46
46
47
47
```json
48
48
{
@@ -88,7 +88,7 @@ The following JSON document is an example of the SQL Server - Azure Arc resource
88
88
| Backup information |`backupInformation`|`object`|
89
89
| Provisioning state |`provisioningState`|`string`|
90
90
91
-
The following JSON document is an example of the SQL Server database - Azure Arc resource.
91
+
The following JSON document is an example of the [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] database - Azure Arc resource.
92
92
93
93
```json
94
94
{
@@ -116,6 +116,6 @@ The following JSON document is an example of the SQL Server database - Azure Arc
116
116
117
117
## Related content
118
118
119
-
-[Automatically connect your SQL Server to Azure Arc](automatically-connect.md)
120
-
-[Configure advanced data security for your SQL Server instance](configure-advanced-data-security.md)
121
-
-[Configure best practices assessment on an Azure Arc-enabled SQL Server instance](assess.md)
119
+
-[Automatically connect your [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] to Azure Arc](automatically-connect.md)
120
+
-[Configure advanced data security for your [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] instance](configure-advanced-data-security.md)
121
+
-[Configure best practices assessment on an Azure Arc-enabled [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] instance](assess.md)
-[!INCLUDE [ssnoversion-md](../../../includes/ssnoversion-md.md)] roles other than the Database Engine, such as Analysis Services (SSAS), Reporting Services (SSRS), or Integration Services (SSIS).
13
13
-[!INCLUDE [ssnoversion-md](../../../includes/ssnoversion-md.md)] editions: Business Intelligence.
14
+
- Private Link connections to the Azure Arc data processing service at the `san-af-<region>-prod.azurewebsites.net` endpoint used for inventory and usage upload.
14
15
-[!INCLUDE [sql2008-md](../../../includes/sql2008-md.md)], [!INCLUDE [sql2008r2-md](../../../includes/sql2008r2-md.md)], and older versions.
15
16
- Installing the Arc agent and [!INCLUDE [ssnoversion-md](../../../includes/ssnoversion-md.md)] extension can't be done as part of sysprep image creation.
16
17
-[!INCLUDE [ssnoversion-md](../../../includes/ssnoversion-md.md)] in Azure Virtual Machines.
Copy file name to clipboardExpand all lines: docs/sql-server/end-of-support/sql-server-extended-security-updates.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -335,9 +335,9 @@ Now you can continue to the [Confirmation](#confirmation) section.
335
335
336
336
1. We recommend you use a year-specific tag to link your [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] instances to your ESU invoice number for easy reference. For example:
337
337
338
-
- First year: `Year1OrderID`
339
-
- Second year: `Year2OrderID`
340
-
- Third year: `Year3OrderID`
338
+
- First year: `Year1InvoiceID`
339
+
- Second year: `Year2InvoiceID`
340
+
- Third year: `Year3InvoiceID`
341
341
342
342
> [!NOTE]
343
343
> If you use Azure services such as Azure Dedicated Host, Azure VMware Solution, Azure Nutanix Solution, and Azure Stack (Hub, Edge, and HCI), you can set the ESU invoice number to `InvoiceNotNeeded`.
Copy file name to clipboardExpand all lines: docs/ssdt/ssis-vs2019-troubleshooting-guide.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,8 +55,10 @@ If you install successfully, but the solution shows **"incompatible"**, and "The
55
55
1. Open Visual Studio -> Extension -> Manage Extensions -> Installed
56
56
1. Enable SSIS extension
57
57
1. Relaunch Visual Studio
58
-
59
-
If you get an error during installation, and find **"Bundle action failed: Invalid pointer (0x80004003)"** in the log. You can check the logs under %temp%\SsdtisSetup, the more detail log is under Microsoft.DataTools.IntegrationServices_{timestamp}_ISVsix.log:
58
+
59
+
If you get an error during installation, and find **"Process returned error: 0x80131500"** in the log. You can open %temp%\SsdtisSetup folder, search in Microsoft.DataTools.IntegrationServices_{timestamp}_ISVsix.log:
60
+
- When the error is "Pre-check verification failed with warning(s) : AnotherInstallationRunning.",
61
+
- kill MSIExec.exe in task manager, and retry.
60
62
- When the error is "The file {filefullpath} already exists.":
61
63
1.```
62
64
cd C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE
Copy file name to clipboardExpand all lines: docs/ssdt/ssis-vs2022-troubleshooting-guide.md
+3-10Lines changed: 3 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,16 +93,9 @@ If you install successfully, but the solution shows **"incompatible"**, and "The
93
93
1. Enable SSIS extension
94
94
1. Relaunch Visual Studio
95
95
96
-
If you get an error during installation, and find **"Bundle action failed: Invalid pointer (0x80004003)"** in the log. You can check the logs under %temp%\SsdtisSetup, the more detail log is under Microsoft.DataTools.IntegrationServices_{timestamp}_ISVsix.log:
97
-
- When the error is "The file {filefullpath} already exists.":
98
-
1.```
99
-
cd C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE
If you get an error during installation, and find **"Process returned error: 0x80131500"** in the log. You can open %temp%\SsdtisSetup folder, search in Microsoft.DataTools.IntegrationServices_{timestamp}_ISVsix.log:
97
+
- When the error is "Pre-check verification failed with warning(s) : AnotherInstallationRunning.",
98
+
- kill MSIExec.exe in task manager, and retry.
106
99
- When the error is "Object reference not set to an instance of an object.",
107
100
- delete the broken instance folder "%ProgramData%\Microsoft\VisualStudio\Packages\_Instances\<InstallationID>"
108
101
- When the error is "Error 0x80091007: Failed to verify hash of payload",
0 commit comments