September 21, 2012 at 6:19 pm
Hello,
How do I query the database for all types of constraints such as Primary Key,Foreign Key, Unique Key, and Default Constraint, and rename its system generate name to a name in following format:
- PK<TableName>_ColumnName1_ColumnName2
- FK<TableName>_ColumnName1
- UK<TableName>_ColumnName1_ColumnName2
- DF<TableName>_ColumnName1
September 21, 2012 at 9:12 pm
September 21, 2012 at 9:15 pm
Thanks!
The link covers Primary Key and Default Constraint, but not the Foreign Key and Unique Constraint.
Do you have any pointers on those?
September 24, 2012 at 1:14 am
anonymous2009 (9/21/2012)
Thanks!The link covers Primary Key and Default Constraint, but not the Foreign Key and Unique Constraint.
Do you have any pointers on those?
This may help you to find UNIQUE and Foreign Key Constraints:
SELECT *
FROM information_schema.constraint_column_usage a
LEFT OUTER JOIN information_schema.table_constraints b
ON a.CONSTRAINT_CATALOG = b.CONSTRAINT_CATALOG AND
a.CONSTRAINT_SCHEMA = b.CONSTRAINT_SCHEMA AND
a.TABLE_CATALOG = b.TABLE_CATALOG AND
a.TABLE_SCHEMA = b.TABLE_SCHEMA AND
a.CONSTRAINT_NAME = b.CONSTRAINT_NAME
WHERE CONSTRAINT_TYPE IN ('FOREIGN KEY', 'UNIQUE')
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St
September 24, 2012 at 1:35 am
You can also get these from SYS tables if you prefer:
SELECT b.name, b.object_id, b.parent_object_id, b.type_desc
FROM sys.all_objects a
INNER JOIN sys.key_constraints b
ON a.object_id = b.parent_object_id
WHERE b.type_desc = 'UNIQUE_CONSTRAINT'
UNION ALL
SELECT b.name, b.object_id, b.parent_object_id, b.type_desc
FROM sys.all_objects a
INNER JOIN sys.foreign_keys b
ON a.object_id = b.parent_object_id
WHERE b.type_desc='FOREIGN_KEY_CONSTRAINT'
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply