Unique Key Violation in SQL Server - Is it safe to assume Error 2627?

Question

I need to catch violation of UNIQUE constraints in a special way by a C# application I am developing. Is it safe to assume that Error 2627 will always correspond to a violation of this kind, so that I can use

if (ThisSqlException.Number == 2627) {     // Handle unique constraint violation. } else {     // Handle the remaing errors. } 

?

Answer 1

2627 is unique constraint (includes primary key), 2601 is unique index

SELECT * FROM sys.messages WHERE text like '%duplicate%' and text like '%key%' and language_id = 1033 

Answer 2

Here is a handy extension method I wrote to find these:

    public static bool IsUniqueKeyViolation(this SqlException ex)     {         return ex.Errors.Cast<SqlError>().Any(e => e.Class == 14 && (e.Number == 2601 || e.Number == 2627 ));     }