A
Ahmed Jewahar
Hi All,
I'm looking for an Ideal and best logic towards open a database
connection to SQL server 2000 from an ASPX pages.
I have desinged an Intranet application. But I don't know that I have
applied an ideal logic to open a connection from my application.
Below is the details of my applicaiton:
Application : ASP.NET Intranet Application
WebServer: IIS Server
Backend Database : SQL Server 2000. Configured as "Use SQL Server
Authenticaiton"
I have about 60+ users who use my Inreanet application extensivley daily
basis. We have many remote users (using leased line) within our Network
(VAN).
I have created "Login" for each users in SQL Server 2000 and all of them
added (user) to all the Database. In my application, there is a "Login"
form where all the usres must enter their "Login" to enter the
applicaiton.
I'm using the above login to open a "Connection" to my SQL server. For
example if there are 50 user accessing my Intranet Application, there
would be 50 Connection will opened at Database !. I'm afraid this might
cause my database performance.
My questions are :
a) Can I use a Common "Login" for all the userd to open a "Connection"
to my SQL Server 2k. ? Will it incerase the performance of my
application as conneciton string can be utilized from "Pooling" ?.
b) If I user One 'Login" for all the users to open a connection, I won't
be able to monitor each users activity (from SQL profiler). Isn't it ?.
c) What's is normal method people are following or MS suggesting towards
this type of situaitons ?
d) Also In my application there are server ASPX pages which are
basically for various reporting and analysis purpose. In every page, I
OPEN the "Connection" and CLOSE at the end of the process. But not using
"cn1.Dispose" in order to utilise the conneciton from "Pooling" .
Kindly share all of your expertise in this area. I would be more than
happy to follow best logic of yours.
Expecting quick reply and really appreciate for it.
Hope my quiery make sense. Otherwise pls let me know so I can give more
details. I'm not good at writing.
Many thanks in advance..
I'm looking for an Ideal and best logic towards open a database
connection to SQL server 2000 from an ASPX pages.
I have desinged an Intranet application. But I don't know that I have
applied an ideal logic to open a connection from my application.
Below is the details of my applicaiton:
Application : ASP.NET Intranet Application
WebServer: IIS Server
Backend Database : SQL Server 2000. Configured as "Use SQL Server
Authenticaiton"
I have about 60+ users who use my Inreanet application extensivley daily
basis. We have many remote users (using leased line) within our Network
(VAN).
I have created "Login" for each users in SQL Server 2000 and all of them
added (user) to all the Database. In my application, there is a "Login"
form where all the usres must enter their "Login" to enter the
applicaiton.
I'm using the above login to open a "Connection" to my SQL server. For
example if there are 50 user accessing my Intranet Application, there
would be 50 Connection will opened at Database !. I'm afraid this might
cause my database performance.
My questions are :
a) Can I use a Common "Login" for all the userd to open a "Connection"
to my SQL Server 2k. ? Will it incerase the performance of my
application as conneciton string can be utilized from "Pooling" ?.
b) If I user One 'Login" for all the users to open a connection, I won't
be able to monitor each users activity (from SQL profiler). Isn't it ?.
c) What's is normal method people are following or MS suggesting towards
this type of situaitons ?
d) Also In my application there are server ASPX pages which are
basically for various reporting and analysis purpose. In every page, I
OPEN the "Connection" and CLOSE at the end of the process. But not using
"cn1.Dispose" in order to utilise the conneciton from "Pooling" .
Kindly share all of your expertise in this area. I would be more than
happy to follow best logic of yours.
Expecting quick reply and really appreciate for it.
Hope my quiery make sense. Otherwise pls let me know so I can give more
details. I'm not good at writing.
Many thanks in advance..