>In the book I use (SQL 2005 Unleashed) the author is using the following naming convention for UNIQUE constraint:
>AK_TABLENAME_FIELDNAME
>
>Do you think AK stands for Alternative Key? Or what else could it be?
>
>Also, how important and where do you use the names of constraints (other than when you create them)?
If you need to drop a constraint, you need a name.
If it's not broken, fix it until it is.
My Blog