SQL layouts

As a developer, what is a good way to learning database tables layouts? There are multiple db, tables and views. What should I focus on first?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

choose one db at a time
investigate those tables
then look at the views

is this what you are looking for?
ps: I'm not sure what you mean by "layout"

+edit: what tools do you have to access the dbs?
VBdotnet2005Author Commented:
I just started my new job. There are many tables, views and store procedures. I just a need good good way to approach them.
VBdotnet2005Author Commented:
I am using Microsoft SQL Server Management Studio for 2008r2
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Diagrams are often a nice way to start with unfamiliar dbs.
Perhaps there are already some diagrams - ask your co-workers

Try looking at this youtube vid (esp. the beginning 2.5 minutes or so)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
nemws1Database AdministratorCommented:
I like to start with the views.  It'll give you a few ideas on how tables are joined.  Identify which tables require a foreign key from other tables.  Reports are a good source for this as well.  *Hopefully* there is some sort of consistent naming convention.  Also, look at any code that accesses the database (either stored procedures or client-side code).  The goal is try to identify the relationships, not just what data is where (that'll come to automatically later).  Use 'EXEC sp_help <object_name>' a LOT.  (EXEC sp_helptext 'proc_name' for stored procedures).
David ToddSenior DBACommented:

If in a MS shop, grab a copy of Viso and create a diagram or two per database and print it out. Viso can "reverse engineer" a database and show the relation between tables based on the foreign key attributes etc.

Once you get that then take a look at a small sample of whats in the table. ie select top 100 * from dbo.sometable order by newid()

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.