Re: What are some ADO & ASP.NET best practices

From: Scott Allen (bitmask_at_[nospam)
Date: 05/09/04 

Date: Sun, 09 May 2004 10:03:42 -0400

Hi Rashad:

Keeping connection objects around in global state will kill
scalability. Transactions are generally bad for performance, but
required for data integrity.

What is the serious problem you are encountering? The first step would
be to use tools like ACT, SQL Profiler, and Perfmon to identify where
botlenecks occur. Maybe it's a common query in your database not using
an index, or perhaps your ASP.NET has a problem and the database is
under utilized. There is a *wealth* of information in the following
document, including how to measure performance, with chapters
dedicated to ADO.NET and SQL Server performance tips:

Improving .NET Application Performance and Scalability
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/scalenet.asp

HTH, 

--
Scott
http://www.OdeToCode.com
On Sat, 8 May 2004 18:15:35 -0400, "Rashad Rivera"
<rashadrivera.I_HATE_SPAM@SPAM_REALLY_SUCKS.hotmail.com> wrote:
>What is the best practice for querying, inserting and deleting from a SQL
>2000 database from high traffic ASP.NET web forms?  Is it to have the
>SqlConnection & SqlCommand object initialized and stored globally in the
>Application object, or is it to dynamically create and destroy them with
>every visit to the web forms?  I am seeing a serious problem with
>performance when I got to over 1000 users consecutively.  I estimate a usage
>of over 10,000.
>
>
>
>If I am to store the SqlConnection and Command objects in the global
>Application object, how will I deal with threading, or is IIS single
>threaded?
>
>
>
>How do sites like Google perform their queries?  They must be in the million
>hit range.
>
>
>
>My next question is will transactions help to improve performance?  And if
>so, where can I find completed samples?
>
>
>
>I know I have a lot of question and I thank you for your help in advance.
>
>
>
>Sincerely,
>
>
>
>- Rashad Rivera
>

Relevant Pages

  • Re: OOP/OOD Philosophy
    ... > Because if you don't Oracle will print something you don't want to see. ... The database should not print anything at all. ... > Great but this discussion was about Standand SQL. ... Transactions and locking work together. ...
    (comp.object)
  • table gone!
    ... We have a 2005 SQL with a database that has a very important table where all ... of our users' transactions are kept. ... and we had no maintenance plan running so there is no backup of the database. ...
    (microsoft.public.sqlserver.server)
  • Re: Support for XA
    ... I have a need to share an oracle ... but not directly at the database level. ... that sits on top of whatever database transactions are active through ... After all the databases' SQL statements have ...
    (perl.dbi.users)
  • replicate data since last backup/detach
    ... I am required to move a production database to a new sql server (on another ... Is there a way to set up replication so that only transactions since the ...
    (microsoft.public.sqlserver.replication)
  • Re: Do Transactions guard against corruption?
    ... when the database is opened and closed. ... meant by 'corruption'. ... Transactions have NEVER been designed as safeguard for those previous ... not used by Access to protect the structure of the database. ...
    (microsoft.public.access.modulesdaovba)
Loading