Identify Primary Key Violation Prior to Insert (Updated)

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Article Discussions » Article Discussions by Author » Discuss content posted by kgayda » Identify Primary Key Violation Prior to...

Identify Primary Key Violation Prior to Insert (Updated)

Rate Topic

Display Mode

Topic Options

Author

Message

kgayda

Posted Monday, October 08, 2007 2:06 PM

SSC Veteran

Group: General Forum Members
Last Login: Tuesday, April 19, 2011 5:10 PM
Points: 275, Visits: 168

Comments posted to this topic are about the item Identify Primary Key Violation Prior to Insert (Updated)

Karen Gayda
MCP, MCSD, MCDBA

gaydaware.com

Post #408171

kgayda

Posted Wednesday, October 10, 2007 1:22 PM

SSC Veteran

Group: General Forum Members
Last Login: Tuesday, April 19, 2011 5:10 PM
Points: 275, Visits: 168

For more detail on using this procedure, read the SQL Team article that I posted: http://www.sqlteam.com/article/anticipating-primary-key-violations

This gives step-by-step instructions on how to get the most out of this procedure.

Karen Gayda
MCP, MCSD, MCDBA

gaydaware.com

Post #409222

mescotty22

Posted Thursday, February 19, 2009 6:29 AM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, August 24, 2011 8:36 AM
Points: 6, Visits: 121

What ever happened to simply grouping by the primary key with a count > 1? Wouldn't that find dupes just as well? It seems like overkill to run each record through a cursor against multiple functions.

Post #660235

kgayda

Posted Thursday, February 19, 2009 7:03 AM

SSC Veteran

Group: General Forum Members
Last Login: Tuesday, April 19, 2011 5:10 PM
Points: 275, Visits: 168

It doesn't work in every scenario. The proc. that I wrote handles every condition possible that I had encountered.

Karen Gayda
MCP, MCSD, MCDBA

gaydaware.com

Post #660265

« Prev Topic | Next Topic »

Permissions