While I have been blogging about SQL Server for a long time, I still believe that there is still a lot of error which are not discovered by me. It is always fun to see new error and find a fix for the issue. Let us see how to fix error related to MERGE statement.
Here is one of the errors which I encountered while preparing for a demo.
Msg 8672, Level 16, State 1, Line 19
The MERGE statement attempted to UPDATE or DELETE the same row more than once. This happens when a target row matches more than one source row. A MERGE statement cannot UPDATE/DELETE the same row of the target table multiple times. Refine the ON clause to ensure a target row matches at most one source row, or use the GROUP BY clause to group the source rows.
While the error message was telling me the issue, I wanted to know how to avoid it. Here is the sample code which anyone can use and reproduce the same error.
SET NOCOUNT ON GO USE tempdb GO CREATE TABLE Employee(EmpID INTEGER,EmpName VARCHAR(15) ) GO INSERT INTO Employee VALUES(1,'Pinal') INSERT INTO Employee VALUES(2,'SQLServer') INSERT INTO Employee VALUES(1,'SQLAuthority') GO CREATE TABLE EmployeeSalary (EmpID INTEGER ,Salary INTEGER) GO INSERT INTO EmployeeSalary VALUES(1,235) INSERT INTO EmployeeSalary VALUES(2,255) GO MERGE EmployeeSalary AS es USING (SELECT EmpID,EmpName FROM Employee) AS m ON es.EmpID = m.EmpID WHEN MATCHED THEN update SET es.Salary = es.Salary + 25;
Looking at the error message, it is clear that the merge statement is trying to update the target table Employee Salary but while doing so, SQL server encountered duplicate entry in the source table (defined as a query)
Hence, here in the table Employee which is the source table in Merge statement, there are two similar entries for EmpID (1) . This tries to update the target the table Employee Salary which has one unique record for this EmpID. Hence this operation is not allowed in Merge and it throws the above error when duplicate entry is seen in the source table (column ref in ON clause in Merge).
WORKAROUND / SOLUTION
To Resolve this issue, we need to remove the duplicate data from the source entities or to prevent such errors from being triggered. We can also create primary key constraints on fields referred in the ON clause of the Merge statement.
Reference: Pinal Dave (http://blog.SQLAuthority.com)
First appeared on SQL SERVER – FIX : Error Msg 8672 – The MERGE Statement Attempted to UPDATE or DELETE the Same Row More Than Once
One of my client was trying to start SQL Service and it was failing. I asked to hare ERRORLOG so that we will get some idea about the cause. Here is the information from ERRORLOG file.
One of my client was unable to modify the maintenance plan using SSMS. When we did various tests, we found that existing maintenance plans could execute and work. We tried creating a new maintenance plan and found it to be working. So, our issue is confined to “unable to modify existing plans”. Here is the error message
As a part of my passion, I try to help people in fixing simple issues and explain the behavior by looking at logs. Here is an email from my friend about Availability Group Missing or Deleted Automatically.
This blog is an outcome of an email communication with my client. The issue was that they were having big tempdb files. They had multiple files and of uneven size. As soon as they restart SQL, the initial size itself was huge and when they tried to shrink the TempDB database, it was not doing anything. Here was the message in SQL Server Management Studio query window.
My learning is always fun. I strongly believe that unless you break something, you can’t learn how to fix them. While writing a new blog about auditing, I faced an interesting error. So, I thought of writing my findings before I write the actual blog. Let us learn about Audit failed to start Error 33222.
One of my clients contacted me in assistance to install SQL Server. Generally, this is straightforward, but sometimes there are problems. This time we received an error message and it was very interesting. Let us learn about error related to the XML Document.
Once there was a security breach on my client machine and they wanted to know who made changes to the SysAdmin role. They contacted me and my first question was that, are you are auditing such changes and as expected answer was No. I gave them answer that nothing can be done as a consultant. They still wanted my suggestion to prevent this in future. So, they want to track if someone does such things in future. Let us see a script to audit login and role member change.
Learning never stops for me with SQL Server. Even though I have written articles to solve many issues, I still get pinged from various clients and I find one new thing every day. In this blog post we will learn how to fix the error related to installing the service pack in the cluster.