Results 1 to 4 of 4
  1. #1
    Join Date
    Nov 2003

    Unanswered: Optimum database for Web based applications

    Hello everyone!

    Which database is optimum for web based applications?

    If there is a webpage, which at any point of time, is accessed by tens of thousands of people across the world. Which database would be better suited to this type of web application where there is huge online traffic?

    Can anyone put across how each database like Microsoft SQL, Sybase, Oracle, etc., performs with a Web application, which is
    1)ASP based
    2)JSP based

    What are the intricacies involved in selecting a database for a Web based application?

    Write back

    Any reference to these details is also appreciated.


  2. #2
    Join Date
    Aug 2002
    I would go with SQL Server as not much exp. with ORACLE, check for all details and information.
    --Satya SKJ
    Microsoft SQL Server MVP

  3. #3
    Join Date
    Feb 2002
    How many concurrent connections will you have ? And how long will the connections persist ? What exactly will the web application do ? Are you load balancing to multiple sql server machines ?

  4. #4
    Join Date
    Oct 2003


    The first and perhaps the most importants step for you is... to decide what the selection criteria ought to be. What's important and unimportant to this application? How much load will it receive? What's the budget, the sensitivity of the data and so-on? Under what operating-system(s) will it run?

    Perhaps the most critical factor, for a high-volume web database, is that of load balancing and throttling so that the system never attempts to do more than it is physically capable of. e.g.: If 5,000 requests crash in within one second, which is quite possible, but the system is capable of handling only 2,500 and it posesses mechanisms to ensure that only 2,500 requests are attempted (the rest are queued, for a mere one second more), then the system will handle the workload gracefully without popping a piston.

    This doesn't involve the DBMS selection directly, but it's definitely part of the overall picture ... and when an un-controlled overload occurs, the DBMS is usually the one that is (wrongly) blamed.
    ChimneySweep(R): fast, automatic
    table repair at a click of the

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts