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: support/sql/azure-sql/sql-installation-fails-sector-size-error-azure-vm.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,11 @@
1
1
---
2
2
title: SQL Server Installation Fails with Sector Size Error on Azure VM
3
3
description: Resolves the error (Cannot use file master.mdf because it was originally formatted with sector size 4096) when you try to install a SQL Server instance on an Azure VM running Windows.
Copy file name to clipboardExpand all lines: support/sql/database-engine/replication/update-statements-replicated-as-delete-insert.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
---
2
-
title: Update is replicated as DELETE/INSERT pairs
2
+
title: Update Is Replicated as DELETE or INSERT Pairs
3
3
description: This article describes that Update statements may be replicated as DELETE/INSERT pairs.
4
-
ms.date: 11/15/2024
4
+
ms.date: 03/20/2025
5
5
ms.custom: sap:Replication, Change Tracking, Change Data Capture, Synapse Link
6
-
ms.reviewer: RAJUGIRD
6
+
ms.reviewer: RAJUGIRD, ansavio
7
7
ms.topic: reference-architecture
8
8
---
9
9
# UPDATE statements may be replicated as DELETE/INSERT pairs
@@ -39,7 +39,7 @@ UPDATE TABLE1 set col1 = 3 where col3 = 'Dallas'
39
39
40
40
The `UPDATE` statement is implemented by SQL Server as a pair of `DELETE`/`INSERT` statements since you're updating `col1`, which has a unique index defined. Thus, the log reader places a pair of `DELETE`/`INSERT` calls in the distribution database. This can impact any business logic that is present in the triggers or custom stored procedures at the Subscriber. You should incorporate the additional business logic in `DELETE` and `INSERT` triggers or stored procedures to handle this situation.
41
41
42
-
If you prefer to use single logic and you want all your `UPDATE`commands replicated as`DELETE`/`INSERT` pairs, you can enable [Trace Flag 8207](/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql#tf8207).
42
+
If you prefer to replicate single-row updates as `UPDATE`statements instead of`DELETE` or `INSERT` pairs, you can enable [Trace Flag 8207](/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql#tf8207).
43
43
44
44
Additionally, if you use a horizontal filter in your publication and if the updated row doesn't meet a filter condition, only a `DELETE` procedure call is sent to the subscribers. If the updated row previously didn't meet the filter condition but meets the condition after the update, only the `INSERT` procedure call is sent through the replication process.
By using the exec subsystem command approach, you add verbose console logging switches to the SSIS command line to call the Dtexec.exe SSIS command-line executable file. Additionally, you use the Advanced job feature of the output file. You can also use the **Include Step Output in the history** option to redirect the logging information to a file or to the SQL Server Agent Job History.
93
93
94
-
The following is an example of a command line:
94
+
Here's an example of a command line:
95
95
96
96
```console
97
97
dtexec.exe /FILE "C:\_work\SSISPackages\ProtectionLevelTest\ProtectionLevelTest\AgentTesting.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING V /CONSOLELOG NCOSGXMT
98
98
```
99
99
100
-
The console logging returns details that resemble the following:
100
+
The console logging returns details that resemble the following messages:
101
101
102
102
```output
103
103
Error: 2006-04-27 18:13:34.76 Code: 0xC0202009 Source: AgentTesting Connection manager "(local).msdb" Description: An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Login failed for user 'DOMAINNAME\username'.". End Error
- For more information about a similar problem, see [You receive an "Error loading" error message when you try to run a SQL Server 2005 Integration Services package in SQL Server 2005](https://support.microsoft.com/help/904800)
117
-
118
-
- For more information about how to use the Dtutil.exe utility in batch operations, see [How to use the dtutil utility (Dtutil.exe) to set the protection level of a batch of SQL Server Integration Services (SSIS) packages in SQL Server 2005](https://support.microsoft.com/help/906562)
119
-
120
-
- For more information about how to create package templates, see [How to create a package template in SQL Server Business Intelligence Development Studio](https://support.microsoft.com/help/908018)
121
-
122
-
- For more information about SSIS package security and the `ProtectionLevel` property, see the **Security Considerations for Integration Services** topic in SQL Server 2005 Books Online.
123
-
124
-
Unfortunately, users are not aware that default agent job step settings put them in this state. For more information about SQL Server Agent proxies and SSIS, see the following topics in SQL Server 2005 Books Online:
125
-
126
-
- Scheduling package execution in SQL Server Agent
127
-
- Creating SQL Server Agent proxies
116
+
- For more information about a similar problem, see [You receive an 'Error loading' error message when you try to run a SQL Server Integration Services package](../integration-services/error-loading-message-run-integration-services-package.md).
117
+
-[Connectivity error 0x80004005 occurs when you run an SSIS package as a SQL Agent job](../database-engine/connect/sql-server-faces-connectivity-issue-ssispack-fail.md).
118
+
- For more information about how to create package templates, see [Create a package in SQL Server Data Tools using the Package Template](/sql/integration-services/create-packages-in-sql-server-data-tools#create-a-package-in-sql-server-data-tools-using-the-package-template).
119
+
- For more information about SSIS package security and the `ProtectionLevel` property, see [Protection Level Setting and the SSISDB Catalog](/sql/integration-services/security/access-control-for-sensitive-data-in-packages#protection-level-setting-and-the-ssisdb-catalog).
_Applies to:_ SQL Server 2019, SQL Server 2017, SQL Server 2016
13
13
14
+
## Historical servicing baselines
15
+
14
16
Historically, servicing baselines (RTM or Service Pack) have included the following servicing branches:
15
17
16
18
- A General Distribution Release (GDR) branch that contains only security and other critical fixes.
17
19
- A cumulative update (CU) branch that contains security and other critical fixes plus all other fixes for the baseline.
18
20
21
+
## Microsoft update detection logic
22
+
19
23
The Microsoft Update (MU) detection logic was constructed so that instances at the servicing baseline or along the GDR branch would be offered updates from the GDR branch.
20
24
21
25
Previously, users had to proactively install at least one CU to align the instance to the CU branch for servicing through MU. However, after that was done, you could not return to the GDR branch for that instance until either of the following changes were made:
@@ -25,13 +29,23 @@ Previously, users had to proactively install at least one CU to align the instan
25
29
26
30
This logic was established to minimize the changes to the instance if a security update or other critical update was required. Instances on the CU branch have to take all updates that are released for the baseline when a required security or other critical release appears. This includes all nonsecurity changes up to the required security update.
27
31
28
-
However, this logic created problems for users who tried to manage routine servicing of large sets of instances by using WSUS. This is because the MU logic couldn't be used without first manually updating every client so that it could participate. To work around this issue and still avoid flipping instances to the CU train without explicit user consent, the following changes were made to the MU detection logic for both routine CU servicing and security releases for the more recent servicing releases of baselines in support:
32
+
### Problems with MU logic
33
+
34
+
However, this logic created problems for users who tried to manage routine servicing of large sets of instances by using WSUS. This is because the MU logic couldn't be used without first manually updating every client so that it could participate.
35
+
36
+
### Changes to MU detection logic
37
+
38
+
To work around this issue and still avoid flipping instances to the CU train without explicit user consent, the following changes were made to the MU detection logic for both routine CU servicing and security releases for the more recent servicing releases of baselines in support:
29
39
30
40
- Cumulative Updates: The MU detection logic now allows clean instances that are at the baseline (RTM or SP, with no servicing updates) or that are already updated along the CU branch to receive the update. A CU update does not have to be installed for an instance to be offered the update. However, if the instance has a GDR update, the instance must still be manually updated outside MU to become manageable through MU (WSUS) automation.
31
41
- Security Releases (GDRs): The logic for security releases is now split into the following channels:
42
+
32
43
- An *Automatic Updates* channel (Microsoft Update) keeps the older historic behavior that requires a CU to be installed on the instance in order for the CU branch version of the security release to be offered. It does this to protect instances from receiving all updates instead of only critical and security-related updates without evidence of the user explicitly opting in to the more extensive mode of servicing.
44
+
33
45
- A *WSUS / Catalog* channel that uses the new detection logic that allows the CU branch version of the security release to be applied against a clean baseline instance. This is the channel of the release that will be presented to users who go to the Microsoft Update Catalog website.
34
46
47
+
## Applicable releases
48
+
35
49
This new updated detection logic applies to the following CU and GDR releases:
36
50
37
51
- SQL Server 2016 Service Pack 2: CU14 and later CUs
Copy file name to clipboardExpand all lines: support/sql/ssms/error-click-databases-node.md
+27-18Lines changed: 27 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Error when you click the Databases node
3
3
description: This article describes an error message that typically occurs in SSMS when there is a problem retrieving information about one or more databases of a SQL Server instance.
4
-
ms.date: 11/19/2020
4
+
ms.date: 03/21/2025
5
5
ms.custom: sap:SQL Server Management, Query and Data Tools
6
6
---
7
7
# Error message when you click the Databases node in SQL Server Management Studio in SQL Server
You may receive an error message similar to the following when using SQL Server Management Studio (SSMS)
16
+
You might receive an error message similar to the following one when using SQL Server Management Studio (SSMS):
17
17
18
18
> Failed to retrieve data for this request (Microsoft.SqlServer.Management.sdk.sfc)
19
19
20
20
## Troubleshooting
21
21
22
-
There can be multiple causes that can contribute to this problem. The following items may help you understand and troubleshoot theissue:
22
+
There can be multiple symptoms that can contribute to this problem. The following items may help you understand and troubleshoot theissue:
23
23
24
-
-Check if you are running into any known issues listed below and use the resolutions documented in the corresponding articles:
24
+
-**Symptom 1**
25
25
26
-
-[SQL Server 2016 Agent fails to start or “Failed to retrieve data” error when you try to read error log from SSMS 2016](https://support.microsoft.com/help/3185365)
26
+
You might run into known issues in the following articles:
27
+
28
+
-[SQL Server 2016 Agent fails to start or "Failed to retrieve data" error when you try to read error log from SSMS 2016](https://support.microsoft.com/help/3185365)
27
29
28
30
-[KB4550657 - FIX: Error occurs when you interact with SQL Server Agent in SQL Server 2019](https://support.microsoft.com/help/4550657)
29
31
30
-
- You can run into this issue if are using an older version of SSMS and when one of the following conditions is true:
32
+
**Resolution**
33
+
34
+
To solve the known issues, see the resolutions documented in the corresponding articles listed earlier.
35
+
36
+
-**Symptom 2**
37
+
38
+
You can run into this issue if using an older version of SSMS and when one of the following conditions is true:
39
+
40
+
- SQL Server Management Studio can't correctly read one or more databases. Therefore, certain properties of a database can't be retrieved.
31
41
32
-
-SQL Server Management Studio cannot correctly read one or more databases. Therefore, certain properties of a database cannot be retrieved.
42
+
-One or more databases is in an offline mode and you're using an older version of SSMS to connect to that SQL instance hosting this offline database.
33
43
34
-
- One or more databases is in an offline mode and you are using an older version of SSMS to connect to that SQL instance hosting this offline database.
44
+
In these situations, the collection of objects doesn't appear in the **Object Explorer** pane or the **Object Explorer Details** pane. Therefore, certain properties of the database aren't computed as a group in the collection of objects.
35
45
36
-
In these situations, the collection of objects does not appear in the **Object Explorer** pane or in the **Object Explorer Details** pane. Therefore, certain properties of the database are not computed as a group in the collection of objects.
46
+
> [!NOTE]
47
+
> This problem also occurs if you're not a member of the Sysadmins group.
37
48
38
-
> [!NOTE]
39
-
> This problem also occurs if you are not a member of the Sysadmins group.
49
+
**Resolution**
40
50
41
-
To work around this problem, using the older version of SSMS follow these steps:
51
+
To work around this problem, follow these steps:
42
52
43
-
1. Close the error message.
53
+
1. Close the error message.
44
54
45
-
2. Press **F7** to open theObject Explorer Detailspane.
55
+
2. Press **F7** to open the**Object Explorer Details**pane.
46
56
47
-
3. Right-click the column headers, and make sure that only the following columns are selected:
57
+
3. Right-click the column headers, and make sure that only the following columns are selected:
48
58
49
59
- Name
50
60
@@ -54,8 +64,7 @@ There can be multiple causes that can contribute to this problem. The following
54
64
55
65
- Owner
56
66
57
-
4. Right-click theDatabasesnode, and then click Refresh.
67
+
4. Right-click the**Databases**node, and then select **Refresh**.
58
68
59
-
Alternatively, you can download and install SSMS from [Download SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms) and see if the issue goes away. If the issue still occurs with new version of SSMS, see [SQL Server help and feedback](/sql/sql-server/sql-server-get-help) for additional ways to get assistance with your issue.
69
+
Alternatively, you can download and install SSMS from [Download SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms) and see if the issue goes away. If the issue still occurs with the new version of SSMS, see [SQL Server help and feedback](/sql/sql-server/sql-server-get-help) for additional ways to get assistance with your issue.
60
70
61
-
- You are connecting to a SQL Server 2008 R2 or an earlier version of SQL Server and when guest user is disabled in the msdb database. For additional information review [You should not disable the guest user in the msdb database in SQL Server](https://support.microsoft.com/help/2539091)
0 commit comments