Well, let's say that each client has 100,000 users. Would it be faster to search through 100,000 users or 400,000 users? Now lets assume that each of the clients wants access to their client information. Now you have to search on an additional field to generate the same amount of data.
It could be small but it might add up. Why exactly does the manager want to do this? I just can't think of any good reasons but maybe I'm missing something. At 03:15 PM 4/18/02 -0400, you wrote: >Are there any performance issues associated with combined all clients into a >single database? > >Thanks, >Dave Bosky > >-----Original Message----- >From: Mark Warrick [mailto:[EMAIL PROTECTED]] >Sent: Thursday, April 18, 2002 3:09 PM >To: SQL >Subject: Re: sql database/design/security > >NO!! Definitely not. > >Why in the world would you combine all the separate >clients into a single database. That's a really bad >idea for a lot of reasons. > >Keep it the way it is. > >---mark > >--- "Bosky, Dave" <[EMAIL PROTECTED]> wrote: > > Currently each of our clients has their own database > > for their website on > > our sql box. > > Our web manager is considering moving all clients to > > a single database > > called > > clients and use a single login from Cold Fusion to > > access their data. > > Is this the best practice? How do the rest of you > > guys handle setting up and > > accessing client databases? > > > > I thought the best procedure is to give each client > > their own database. > > Create a account with access to only their database. > > > > Restrict sql operations to stored procedures only. > > > > Any input? > > Dave > > > > > > > > > > > > > > > ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
