Hi Bob,

I'm curious as to why you think you need 10 logins to access one SQL Server?
Your question about application pooling is well taken. The way .Net
application pooling works, you generally don't need to manage it at all. It
manages itself. When you re-use a Connection String, a pooled Connection can
be re-used (automatically) by your application. However, with 10 Connection
Strings, you are ensuring at least 10 pooled Connections. It would seem more
efficient to use a single Windows login for all 10 databases, and assign
that one login the necessary permissions it needs for each database. Unless
there's something I'm missing. One reason I can think of for both using
Integrated Security and multiple logins would be if your web app used Active
Directory and required each user to log in as him/herself. If each user had
access to only one database, and not all 10, that would possibly require 10
logins, depending upon how you architect it. However, since your app is
actually the entity that connects to the database, and not each user, it
would probably be better to design your app to use a single login to connect
to all the databases, and business logic to grant or deny access to
individual clients.