Reply to thread

Message: [QUOTE="Cowboy \(Gregory A. Beamer\), post: 1973224"] INLINE Correct, although there are ways to have accounts. Commerce Server comes to mind. This definitely makes things scalable, as you have a single pool to work from with one user. But the question of accounts is more a security issue, as all auditing is on your shoulders if you use forms auth. This is not a bad thing, just a reality. The pooling mechanism in the SqlClient lib handles pooling. Whether you take control or let ADO.NET handle it, there is a pool, at least by default. If your focus is the number of users, I see nothing wrong with your approach. I think you might want to cluster the web server and the database server at some point in time (at minimum, add a failover), but the programming approach is not a major concern. [/QUOTE]