That's too bad. I suggest purchasing a better hosting service. ---mark
--- "Bosky, Dave" <[EMAIL PROTECTED]> wrote: > Unfortunately we are not allowed to setup a > databases and create logins > For our web clients, we must submit a request to > have one of our DBAs do it. > > > Thanks, > Dave Bosky > > > -----Original Message----- > From: Mark Warrick [mailto:[EMAIL PROTECTED]] > Sent: Friday, April 19, 2002 3:11 PM > To: SQL > Subject: RE: sql database/design/security > > Dave, > > The procedure to setup a database and create logins > takes about 2 minutes. Learn how to do it and fire > the DBA if you can't afford him/her. > > ---mark > > --- "Bosky, Dave" <[EMAIL PROTECTED]> wrote: > > We have to let our DBA's create the databases and > > logins so to avoid that > > process we would just create everything in a > single > > database. > > > > Thanks, > > Dave Bosky > > > > -----Original Message----- > > From: Jennifer Larkin [mailto:[EMAIL PROTECTED]] > > Sent: Friday, April 19, 2002 12:55 AM > > To: SQL > > Subject: RE: sql database/design/security > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
