Best Way To Get Rid Of Error Number 2601 SQL Error

PC running slow?

In some cases, your system may display an error code indicating SQL error 2601. This issue can be caused by a number of reasons. g.This error occurs when clients try to insert duplicate index values ​​into a column or columns with only one unique index. Microsoft® SQL Server ™ certainly allows two rows to have the old index value (including NULL) on uniquely indexed columns.

g.

 Server: Msg 2601, Level 16, State 1, Line 1Unable to insert duplicate keyword string into target '

As the error idea suggests, when you insert data into a work table with a unique index and one of our data in the column (s) included in the unique index, if the table already exists, this error message is displayed.

To emphasize, here is a simple table that contains an incomparable index on one of its columns:

 CREATE TABLE [dbo]. [currency] (    [Currency code] symbol (3),   [Currency name] VARCHAR (50))WALKCREATE ONE INDEX [IX_Currency_CurrencyCode] ON [dbo]. [Currency] ([CurrencyCode])WALK

PC running slow?

ASR Pro is the ultimate solution for your PC repair needs! Not only does it swiftly and safely diagnose and repair various Windows issues, but it also increases system performance, optimizes memory, improves security and fine tunes your PC for maximum reliability. So why wait? Get started today!

The following script populates the table with currency code data:

 INSERT INTO [dbo]. [Currency] ([CurrencyCode], [CurrencyName])VALUES ('U' usd ',. S. Dollar')INSERT INTO [dbo]. [Currency] ([currency name] [currency code],)VALUES ("EUR", "Euro")INSERT INTO [dbo]. [Currency] ([CurrencyCode], [CurrencyName])VALUES 'GBP', ('Pound Sterling')INSERT INTO [dbo]. [Currency] ([CurrencyCode], [CurrencyName])VALUES ("INR", "Indian Rupee")

If the same script is accidentally executed, the following error message is often generated for each INSERT statement executed:

 Msg 2601, Level 14, State 1, Line 2Unable to insert duplicate string of keys into toy 'dbo.Currency' with unique index 'IX_Currency_CurrencyCode'.

Another way to run into some errors is to put the data in one office and the data is taken from other people’s tables. Here is a scenario that highlights this scenario.

 CREATE TABLE [dbo]. [Currency_New] (    [Currency code] CHAR (3),    [Currency name] VARCHAR (50))WALKINSERT INTO [dbo]. ([Currency_new] [CurrencyCode], [CurrencyName])VALUES (CAD, Canadian dollar)INSERT INTO [dbo]. ([Currency_new] [CurrencyCode], [CurrencyName])VALUES (SWF, Swiss francs)INSERT INTO [dbo]. [Currency_New] ([CurrencyCode], [CurrencyName] ()AUD values, Australian dollar)INSERT INTO [dbo]. ([Currency_new] [CurrencyCode], [CurrencyName])VALUES (CAD, Canadian dollar)INSERT INTO [dbo]. [Currency_New] ([CurrencyCode], [CurrencyName])VALUES ('japanese yen', yen ')INSERT INTO [dbo]. [Currency] ([currency code],)SELECT [currency name] [currency code], [named е currencies]FROM [dbo]. [Currency_New] AO DOES NOT EXIST (SELECT FROM 'x' [dbo]. [Currency] B                  O A. [currency code] = B. [currency code])WALK

 Msg 2601, 14, Current State 1, Line 2Unable to insert duplicate baseline into 'dbo.Currency' object with one pointer 'IX_Currency_CurrencyCode'.

As you can see from the script, the original desktop ([dbo]. Contains [currency_new]) has duplicate entries for the Canadian dollar (CAD).

Solution and workaround:

When inserting actual values ​​into a table whose content contains a unique index that serves as the key for the table, there are usually several ways to work around this error message. The first procedure uses an IF statement that checks for new data before executing the INSERT. If the row does not exist in the target table, the concept can be inserted.

This is what the script looks like:

 IF NOT EXISTING (SELECT 'X' FROM [dbo]. [currency]               WHERE [currency code] 'USD') implies INSERT INTO [dbo]. ([currency] [CurrencyCode], [CurrencyName])   VALUES ("US dollars", "US dollars")GO 

ForWriting must occur for each specific real value of the values ​​that are to be inserted into the array.

Another way to check for a row reference in a table is to use the NOT EXISTS SELECT-Comment expression, as shown in the specific script:

after

 INSERT INTO [dbo]. [Currency] [CurrencyCode], ([CurrencyName])SELECT "USD", "US Dollar"WHERE DOES NOT EXIST (SELECT 'X' FROM [dbo]. [Currency]                  WHERE [currency code] = 'USD')GO 

Instead of using the VALUES clause, the statement uses a SELECT statement to insert details into a table. In general, since the information does not come from any table, the FROM clause of the SELECT statement cannot be included. Like all the first parameters, this must be created for each row of data that would normally be inserted into the target table.

When data is loaded from another table and its original table contains duplicates, there are often several ways to avoid errors. The first option is to simply include a DISTINCT clause in the SELECT statement to ensure that only different rows can be inserted into the target table.

Here aboutUpdated version of the generic script for the DISTINCT clause:

 INSERT INTO [dbo]. [Currency] ([CurrencyCode], [CurrencyName])SELECT DISTINCT [currency code], [currency name]FROM [dbo]. [Currency_New] [New]O DOES NOT EXIST (SELECT 'X' [dbo] from. [Currency] [Alt]                 WHERE [New]. [Currency code] = [Old]. [Currency code])GO 

Alternatively, the MERGE statement can be used instead of the INSERT INTO • SELECT WHERE NOT EXISTS statement. The MERGE statement performs insert, update, and / or delete operations on the target table that are performed on the join to the source table.

For this reason, the script looks like a MERGE statement.

 MERGE [dbo] .AS [currency] [target]USED ​​BY (SELECT DIFFERENT [currency code], [currency name]       FROM [dbo]. [Currency_New]) AS [source]On target]. [CurrencyCode] implies [Source]. [Currency code]WHEN MATCH THEN    UPDATE SET [currency name] = [source]. [currency name]IF NOT MEETING, THEN    INSERT ([currency code], [currency name])    VALUES ([source]. [Currency code], [source]. [Currency name]);GO 

As you can see from this MERGE statement, the type table also requires a clauseOther DISTINCT. If the DISTINCT clause is not included, you will likely receive the following error message:

 Msg 8672, Level 16, State 1, Line MERGE 2the statement tried to update or delete the same row multiple times.It starts when the target of the string more closely matches the original string.The MERGE statement has problems updating / deleting the same row multiple times in the concentrate table.Clarify or depend on ON terms to ensure that the target string is usually the same as the original string.GROUP BY clause for grouping original rows.

La Mejor Manera De Descubrir Cómo Deshacerse Del Error De SQL Número 2601
Der Beste Weg, Um Den Fehlernummer 2601 SQL-Fehler Kostenlos Zu Erhalten
Beste Manier Om Van Foutnummer 2601 SQL-fout Af Te Komen
Najlepszy Sposób Na Pozbycie Się Błędu Numer 2601 Błędu SQL
Melhor Maneira De Se Livrar Do Erro Número Do Celular 2601 Erro De SQL
Лучший отличный способ избавиться от ошибки SQL большого количества 2601
Il Modo Migliore Per Eliminare Effettivamente L’errore Numero 2601 Errore SQL
오류 번호 2601 SQL 오류를 안전하게 제거하는 가장 좋은 방법
Bästa Sättet Att Generera Av Fel Nummer 2601 SQL-fel
Meilleur Moyen De Se Débarrasser De L’erreur SQL Numéro 2601

Charlie Saunders

Related posts:

Steps To Get Rid Of Batman Arkham Asylum Launcher 9000 Launch Error Issue Need To Get Rid Of Canon Mp140 E4 Error Issues You Need To Get Rid Of Diablo 3 Error 31 Issues You Need To Get Rid Of HDD DMA Error From Dvr Problems