March 23, 2012 at 11:41 am
I use standard naming conventions but a developer used ERwin to create staging tables in two schemas and he did not use a Name rule to create the Primary Key so it created system generated Primary Keys.
I told him what standard that I wanted to use which is consistent with the article listed below.
So then he publishes the Data Warehouse Tables in the same Database with a different schema.
He only creates Primary Keys, no other constraints but after telling him what I wanted he uses the naming convention XPKTableName.
I never saw anything like it.
To make matters worse I do not see anything that closely resembles fact or dimensions. He must have come up with a new Dimensional Model that I never heard of. :w00t:
http://www.databasedesign-resource.com/constraint-naming-standard.html
Your thoughts and ideas would be greatly appreciated.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
March 24, 2012 at 8:02 am
If you have a published naming standard for your organization then you can enforce that policy. If you don't have one - and this is an issue - you need to develop the naming standard, publish it and get managements approval on the new policy.
If you don't have that - then there really isn't much you can do except go to his manager and try to get them to follow your standards. If they don't want to follow your standards - you can try to work with them to develop their own standards.
If they don't want to follow a standard and you can't get management approval to enforce a standard - not much you can do.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
March 24, 2012 at 9:01 am
They do not work for the company.
But yes, I agree with you that it has to be published and approved. I have not been here that long but I will pull a document that I used for Database Standards that was not limited to naming conventions.
I noticed that on another schema they create a completely different standard for FK's with _FK as the prefix. Talk about consistency.
My standards will be enforced and Management will back me up.
All they have to do is setup or change a rule in ERwin.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
March 24, 2012 at 9:32 am
All that I'm trying to accomplish is making a simplified case as to the benefits of using naming conventions that conform to best practices.
I will prevail no matter what, I just want to make it more palatable and not come across as I'm being a little on the petty side.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply