|
|||||||||
|
|||||||||
| |||||||||
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
Dev Shed Forums Sponsor:
|
|
Get inside! Sample the range of functionality easily built with JMSL Library for Time Series Data Analysis, Heat Maps, Portfolio Optimization, Monte Carlo Simulation, Stock Price Charting and more. Download Now! |
|
#1
August 16th, 2004, 11:50 AM
|
|||
|
|||
Managing SQL Data
Hello,
I am currently working on a large project that will be developed using MS SQL. I have been considering two options when it comes the creation of the database. The first option is to create a sepereate table for each of my clients. The tables would be labeled by their Id number then the tables reqular name. Fore example : 781_Users. The other option is to create a different database for each of the clients. I just need the data to be seperated between clients, it cant mix. Please just give me your opinion on which option you would consider if you were operating a large project. Thanks in advance!
|
|
#2
August 16th, 2004, 11:23 PM
|
|||
|
|||
|
for a "large" project, I don't think you could go wrong w/using a seperate DB for each client...I think it will give you more flexibility and room to grow.
|
|
#3
August 17th, 2004, 10:12 PM
|
||||
|
||||
|
yeah i would create a db for each user. customize the model db and that will create the same db/structure for each client everytime you added someone new.
funner than what i'm workin on. Al
|
|
| Viewing: Dev Shed Forums > Databases > MS SQL Development > Managing SQL Data |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
 |
|
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
