database design

AndyInUK

Hi, We have got hundreds of tables and SPs but no diagram. Basically we just keep on adding new tables as per requirement or delete table and there is no info. What i want to implement now is - a whole database diagram - So what would be the best way keeping in mind that database is big if not huge. Thank You Andyyy

dan sh

Which database? With SQL, it comes as a built in feature. Is that what you are looking for?

50-50-90 rule: Anytime I have a 50-50 chance of getting something right, there's a 90% probability I'll get it wrong...!!

AndyInUK

Yeh it's SQL - sorry i mean Diagram. Should i just use visio and find my way out but that means going through hundreds of tables and sps and understanding them..Looks like i will never get time to sort this out unless there is quicker way which is also good.

dan sh

If you expand the [DatabaseName] node, the first thing you will see is diagram. Although AFAIK, it will not help with stored procedures. You can also check this[^] link. Might be of some help.

50-50-90 rule: Anytime I have a 50-50 chance of getting something right, there's a 90% probability I'll get it wrong...!!

Mycroft Holmes

You need to be careful with SQL diagram designer you could end up applying foreign key constraints while building a diagram. SSMS will not let you save the diagram if the data does not match the constraint, so save OFTEN, this is a good thing but you are going to be VERY frustrated chasing down the data errors. I would use visio unless you actually want to clean up the data. Personally I would opt to clean up the database there are some enormous benefits to be gained from a well structured database.

Never underestimate the power of human stupidity RAH

dan sh

Mycroft Holmes wrote:

I would opt to clean up the database

:thumbsup: Although it would be a bit of pain while cleaning the mess but the in the long run, it is going to be very helpful.

50-50-90 rule: Anytime I have a 50-50 chance of getting something right, there's a 90% probability I'll get it wrong...!!