Reply to thread

Message

[QUOTE="Gordowey, post: 1973206"]
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
[/QUOTE]

Verification