Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
itmasterw
Yak Posting Veteran
90 Posts |
 Posted - 2010-11-21 : 19:00:11
|
Hi,Normally, you would put something like customers in a customer table. and may even break that out into other tables like and address table. But I have heard of DBAs who would put each customer in a separate table so, if an application (like a VB application) was accessing the data for say John Miller all of his data would be in that one table. I would like to know if this is good or bad and why?Thank you  ITM |
|
|
nigelrivett
Master Smack Fu Yak Hacker
3385 Posts |
Posted - 2010-11-21 : 19:27:27
|
| Depends on the system but a table per customer is likely to become unmanageable.Unless you have a static customer base it would mean a change to the database structure for each new customer and a nightmare to maintain any relationships.If you are providing a system for a customer then you might create a new set of tables for each customer to hold all their data - but that would be more likely to be a separate database unless there is a restriction on that.Normally you would hold customer data together. Adresses would normally be in a separate table but cutomer names, IDs and other data in a single table.==========================================Cursors are useful if you don't know sql.SSIS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
itmasterw
Yak Posting Veteran
90 Posts |
Posted - 2010-11-21 : 19:39:04
|
| thanks I appreaciate your thoughts on this.Thank youITM |
|
|
|
|
|
|
Organization and efficentcy question