Text Book advice - DB Design

Question

Text Book advice - DB Design

Minnesota - Viking

Hall of Fame

Points: 3469
More actions
May 31, 2010 at 10:05 am

#387048

Hello guys
I need a textbook to guide me in teh process of a new DB Design. I am designing it from scratch. So i need something that really goes into best practices of DB Design/Planinng etc.
I found this Pro SQL Server 2008 Relational Database Design and Implementation (Paperback)
Your review about this book or your own suggestion is welcome.
Thank You
[font="Verdana"]
Today is the tomorrow you worried about yesterday:-)[/font]

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 1

Very good book.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

PaulB-TheOneAndOnly SSC Guru Points: 66772 More actions · Answer 2

I gather you have little exposure to data modeling, if this is the case a free resource to get a picture of it can be found in http://www.agiledata.org/essays/dataModeling101.html

Just out of curiosity...

- What kind of database are you modeling? ... is it to support OLTP or DSS?

- How big do you expect this database to be in one year time?

- How critical is this database for the user organization?

- How many users do you expect to rely in this database in one year time?

_____________________________________
Pablo (Paul) Berzukov

Author of Understanding Database Administration available at Amazon and other bookstores.

Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

Minnesota - Viking Hall of Fame Points: 3469 More actions · Answer 3

Thanks for the link i think that would be a great resource for me ...

i wish u can throw some light on my other question too

http://www.sqlservercentral.com/Forums/Topic932919-391-1.aspx

Thank You for your curiosity

Here are my answers for your questions

1.OLTP (Receving Data dumps, CSVs, Excels, Text files organizing them into DB i.e finally converting them into one standard format and adding it to DB , Do some processing(Business part.) , Generate Reports , send reports back to clients)

2.Its not created yet but i can expect a intial 1Million rows in roughly 50 tables (most data is varchar,Bit and numeric).. and each year i can expect 2Million new rows (Now u have to tell me the speculative size)

3.Very Critical (100%), but downtime is OK, but not data loss (anyways mgmt plans to move DBs to Cloud storage once created locally)

4. Around 20, mostly to generate reports

[font="Verdana"]
Today is the tomorrow you worried about yesterday:-)[/font]

PaulB-TheOneAndOnly SSC Guru Points: 66772 More actions · Answer 4

allin1 (6/5/2010)
Here are my answers for your questions
1.OLTP (Receving Data dumps, CSVs, Excels, Text files organizing them into DB i.e finally converting them into one standard format and adding it to DB , Do some processing(Business part.) , Generate Reports , send reports back to clients)
2.Its not created yet but i can expect a intial 1Million rows in roughly 50 tables (most data is varchar,Bit and numeric).. and each year i can expect 2Million new rows (Now u have to tell me the speculative size)
3.Very Critical (100%), but downtime is OK, but not data loss (anyways mgmt plans to move DBs to Cloud storage once created locally)
4. Around 20, mostly to generate reports

Glad to help.

It looks to me closer to a DSS rather than OLTP - as far as I gather mostly a reporting database.

Three million rows (total) after one year defines it as a very small database, this is very good news because - please do not take it the wrong way - most design flaws will go unnoticed for years to come. Translation: "you can tackle this project without risking the company's operation and, get a lot of experience in the process".

I would go for the sure thing and model it in the third normal form a.k.a. 3NF - Go for it and have a lot of fun!

_____________________________________
Pablo (Paul) Berzukov

Author of Understanding Database Administration available at Amazon and other bookstores.

Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.