July 8, 2013 at 7:30 am
Hi All,
I am developing a very big project.I have one question about ERD.
I know Normalization is good for big projects BUT I read an article saying that while you are searching in too many tables,Joining them and then find a pattern in it,It will take too much time,so more normalization is not good.
My description is here
"I have Four categories like Properties,Autos,Electronics and jobs. For each categories i have a crawler which gets information from 4 online websites and save in my database.Then i have a website where users can use/search in these informations like any other classified website."
Now i have tables for type,categories and sub categories.For details of each category should i created different table for each website or i should save data in one table?
For example
For Properties i am getting data from http://www.site1.com,www.site2.com,www.site3.com.Now which one will be better either to save in one Properties table for different tables for each like
Properties = site1+site2+site3
OR
Properties_site1 = site1
Properties_site2 = site2 and so on...
Which one will be better to get info and make search in it...
July 8, 2013 at 7:40 am
You probably are not getting any replies because you have the rest of us at an extreme disadvantage here. We can't see your screen and we have no idea what your project is like. Your post just simply has nowhere enough information to begin offering any advice.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
July 8, 2013 at 11:33 am
Methew (7/8/2013)
I know Normalization is good for big projects...
That is plain wrong. For an OLTP system or an Inmon style Data Warehouse normalization is a must. Period.
What happens on small, really small projects is that no matter how crappy data modeling was and how bad queries are written it will still be perceived as performing in an acceptable way.
Methew (7/8/2013)
...BUT I read an article saying that while you are searching in too many tables,Joining them and then find a pattern in it,It will take too much time,so more normalization is not good.
When talking about either an OLTP system or an Inmon style Data Warehouse the statement above is so wrong it gives me a headache.
_____________________________________
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.July 8, 2013 at 12:06 pm
I agree with Paul - normalization is good for any OLTP system. Don't believe everything you read...I would start by not believing the quote above that it isn't good.
That said, if you want anyone to have any chance of helping you, please post DDL to create your tables, DML to populate with sample data and then an example of how you want to search. Without the basics, I can't offer any advice with any confidence.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply