August 11, 2011 at 12:40 am
Hi,
I need help to planning for create best database architecture in sql 2008.
My Cafeteria's are :
Suppose we are planning to create such type of database in which more than 3000 customers
and it may be more than 100 customers record will go for multi trillion. Then rest of 3000-100 = 2900
customer data fetching will be problem.
Then kindly suggest me .......should we create different- different database for each customer or only
single database.
Also suggest me server configuration on which we will put such type of database.
Note : 3000 customers not fix, it can be dynamic....
Regards,
Sachin.
August 11, 2011 at 1:53 am
kumar.sachu08 (8/11/2011)
Hi,I need help to planning for create best database architecture in sql 2008.
My Cafeteria's are :
Suppose we are planning to create such type of database in which more than 3000 customers
and it may be more than 100 customers record will go for multi trillion. Then rest of 3000-100 = 2900
customer data fetching will be problem.
Then kindly suggest me .......should we create different- different database for each customer or only
single database.
Also suggest me server configuration on which we will put such type of database.
Note : 3000 customers not fix, it can be dynamic....
Regards,
Sachin.
What exactly you trying to achieve??
3000 customers not fix, it can be dynamic-What does that mean???
Is there any difference between those 100 and the rest,if yes then you can seperate them on that and create partition.
Do you have an existing database or the number of records are just imagination?
Seperate database for each customer???
August 11, 2011 at 5:03 am
Your description of the problem is confusing and unclear. It sounds like your business users have no idea what they want or that you don't understand what they want.
Before you design anything, you need to sit down with them and collect their actual requirements. What data they need to collect, why they need to collect it, how they want it presented and how they want to get new data into the system. Is this a database that will be serving as a back end to a software tool? What kind of tool will they be using? Is this a database that will collect data from other dbs? These are the sorts of things you need to understand before even starting a database design.
If you don't feel comfortable getting more information from the end users, find someone who is. If you don't know how to create the database, I advise hiring a consultant to come in and do the requirements gathering and design for you. It's the best way to get it done with a minimum of fuss and they can hate the consultant (who gets to leave) for misunderstanding their fuzzy requests instead of hating you (who has to stay and support the database).
This is a huge process you're about to get into. There is too much to say on the issue and not enough space in one thread. Get the requirements first, then start asking us more precise and individual questions as you work through the process. But I still advise hiring outside help for this. The consultant can potentially serve as a teacher as well as a db designer.
August 11, 2011 at 6:08 am
kumar.sachu08 (8/11/2011)
Hi,I need help to planning for create best database architecture in sql 2008.
<snip>
Also suggest me server configuration on which we will put such type of database.
Note : 3000 customers not fix, it can be dynamic....
Hire someone.
Seriously. If you have no idea where to start with a complex database design/system design you are setting yourself up for failure in trying to do it. If you don't get someone in to help with the design, you'll almost certainly have to get someone in later to fix it and tune it.
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
August 11, 2011 at 6:16 am
I agree with Brandie to get the requirements first.
There will be a number of other factors that will play into some decisions on how to architect a database.
So you have customers and sales. I doubt that everything would reside in just 2 tables.
There were a few recent articles about 1NF, 2NF, etc. that if you are not familiar with, would be good to understand the concepts.
And hiring a contractor for such a project might be a good idea.
There will be knowledge transfer, and it could easily have other paybacks.
And there was also a comment of 3000 customers being fixed.
Remember to plan and architect for expected growth.
Good luck!
August 11, 2011 at 10:01 am
I agree with Gail.
If you don't know what your requirements are or if you have requirements and don't know what to impliment then you need to get someone in who will be able to assist you. If you get the design right first time this will save you a lot of blood, sweat and tears (not to mention money) when trying to resolve issues caused by poor design of a solution that does not scale.
Thanks
Chris
August 12, 2011 at 3:40 pm
GilaMonster (8/11/2011)
Hire someone.
I can't argue with that one. That doesn't mean you can't learn from or alongside the person you hire (we all have to start somewhere).
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply