469,945 Members | 1,349 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,945 developers. It's quick & easy.

ASP.net and SQL impersonation for High Scalability

Hi all, I would like to ear your opinion about the best approach for
and ASP.net with high workload traffic (High number of visitors) using
SQL DB

Consider the following scenario:
- Website with 10.000 visitors/day. (and can grows faster. High
Scalability is one of teh requirements)
- Single W2k3 server (no farm),
- ASP.net 1.1 (or ASP.net 2.0) web site
- SQL 2000 (or 2005)

I have the following questions:

1. - I am using "forms" authentication (internet users don't have
a windows account), right?

2. - What about the SQL user? Is it enough to create a single sql user,
and all my visitors connect with this user (i.e.: sqluser)? Only one
sql is enough? and for High Scalability ?

3.- I am using System.Data.SqlClient lib: Should I be worried about
simultaneous connections or Does the SqlClient lib resolves it?

5. - What about connection pooling? Is necessary to implement it?
6. - Is there a better solution for this?

thanks you very much

Any help, comment would be appreciated
Alberto

Oct 2 '06 #1
2 1597
INLINE
"Gordowey" <al************@gmail.comwrote in message
news:11**********************@c28g2000cwb.googlegr oups.com...
Hi all, I would like to ear your opinion about the best approach for
and ASP.net with high workload traffic (High number of visitors) using
SQL DB

Consider the following scenario:
- Website with 10.000 visitors/day. (and can grows faster. High
Scalability is one of teh requirements)
- Single W2k3 server (no farm),
- ASP.net 1.1 (or ASP.net 2.0) web site
- SQL 2000 (or 2005)

I have the following questions:

1. - I am using "forms" authentication (internet users don't have
a windows account), right?
Correct, although there are ways to have accounts. Commerce Server comes to
mind.
2. - What about the SQL user? Is it enough to create a single sql user,
and all my visitors connect with this user (i.e.: sqluser)? Only one
sql is enough? and for High Scalability ?
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.
3.- I am using System.Data.SqlClient lib: Should I be worried about
simultaneous connections or Does the SqlClient lib resolves it?
The pooling mechanism in the SqlClient lib handles pooling.
5. - What about connection pooling? Is necessary to implement it?
Whether you take control or let ADO.NET handle it, there is a pool, at least
by default.
6. - Is there a better solution for this?
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.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com

*************************************************
Think outside of the box!
*************************************************
Oct 2 '06 #2

Cowboy (Gregory A. Beamer) wrote:
INLINE
"Gordowey" <al************@gmail.comwrote in message
news:11**********************@c28g2000cwb.googlegr oups.com...
Hi all, I would like to ear your opinion about the best approach for
and ASP.net with high workload traffic (High number of visitors) using
SQL DB

Consider the following scenario:
- Website with 10.000 visitors/day. (and can grows faster. High
Scalability is one of teh requirements)
- Single W2k3 server (no farm),
- ASP.net 1.1 (or ASP.net 2.0) web site
- SQL 2000 (or 2005)

I have the following questions:

1. - I am using "forms" authentication (internet users don't have
a windows account), right?

Correct, although there are ways to have accounts. Commerce Server comes to
mind.
2. - What about the SQL user? Is it enough to create a single sql user,
and all my visitors connect with this user (i.e.: sqluser)? Only one
sql is enough? and for High Scalability ?

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.
3.- I am using System.Data.SqlClient lib: Should I be worried about
simultaneous connections or Does the SqlClient lib resolves it?

The pooling mechanism in the SqlClient lib handles pooling.
5. - What about connection pooling? Is necessary to implement it?

Whether you take control or let ADO.NET handle it, there is a pool, at least
by default.
6. - Is there a better solution for this?

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.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com

*************************************************
Think outside of the box!
*************************************************


Thanks Gregory,..for your clear explantion..that helps me a lot.

Alberto

Oct 2 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Arpan | last post: by
1 post views Thread by Jimmy | last post: by
9 posts views Thread by pbd22 | last post: by
5 posts views Thread by =?Utf-8?B?S2l0dHlIYXdr?= | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.