Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C#
  4. SQL Server Express - How many querys per a second can it handle?

SQL Server Express - How many querys per a second can it handle?

Scheduled Pinned Locked Moved C#
databasehelpquestionsql-serversysadmin
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    B Offline
    Brad Wick
    wrote on last edited by
    #1

    I have a application I have built that uses a SQL Server express database to store the data. I have built a logging functions which writes the log entrys of whats going on in the application to a text file on the hard disk. When I set the logging to DEBUG mode (which logs a ton of stuff) it takes a long time for certain things to run as its writing a bunch of data to the text file. If they set the logs to WARN... it only writes important information to the log file. This all works great, but I would really like to log everything so if there is a problem with the application I can look at the users log file and tell exactly what they were doing to try and reproduce the error. So I was thinking about writing the logs to the database which would mean I could insert all entrys and just query the items I need to return which brings up my question. If i start to insert a ton of data into the database, at what point could I overload the database? XXX Querys a hour/second? Database reaches XXX size? I know this will depend on the users machine also, but its not going out to a wide user base, more like 10 people.

    A 1 Reply Last reply
    0
    • B Brad Wick

      I have a application I have built that uses a SQL Server express database to store the data. I have built a logging functions which writes the log entrys of whats going on in the application to a text file on the hard disk. When I set the logging to DEBUG mode (which logs a ton of stuff) it takes a long time for certain things to run as its writing a bunch of data to the text file. If they set the logs to WARN... it only writes important information to the log file. This all works great, but I would really like to log everything so if there is a problem with the application I can look at the users log file and tell exactly what they were doing to try and reproduce the error. So I was thinking about writing the logs to the database which would mean I could insert all entrys and just query the items I need to return which brings up my question. If i start to insert a ton of data into the database, at what point could I overload the database? XXX Querys a hour/second? Database reaches XXX size? I know this will depend on the users machine also, but its not going out to a wide user base, more like 10 people.

      A Offline
      A Offline
      Ashfield
      wrote on last edited by
      #2

      Brad Wick wrote:

      I know this will depend on the users machine

      This is just 1 of the considerations. Database design will have a big impact, as will proper connection control and a whole host of other things. I suspect the only real way of finding out is to test it.

      Bob Ashfield Consultants Ltd

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups