This is a bit OT, but you say "we were going to have everybody pass in what company they belonged to and we would know what server and DB to use for that user."
If I were you, I'd force the user to authenticate, and then decide for yourself what company he belongs to. Don't give him the opportunity to lie and tell you the wrong company. I only mention this because I've actually seen a design like this in production, and in that system it was possible to try to lie about your identity. Difficult, but possible. Greg Reinacker Reinacker & Associates, Inc. http://www.rassoc.com -----Original Message----- From: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED]] On Behalf Of franklin gray Sent: Wednesday, May 22, 2002 2:43 PM To: [EMAIL PROTECTED] Subject: Re: Help Architecting A Middle Tier "If you're talking about scaling to 50 users, probably not a big deal. But maybe. If 5000, you definitely want to take a really hard look at your design, and above all else: read "Transactional COM+" by Tim Ewald." The design we are taking is that when we start hosting, we have to keep different clients data in different databases, at least that's what my boss says because the clients wouldn't go for their data sharing a DB with another company. Of course, we can't put to many companies data on one SQL server, so we were going to have everybody pass in what company they belonged to and we would know what server and DB to use for that user. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
