none
Maximum Connections on SQL Server Express 2012 RRS feed

  • Question

  • Hello,

    Can anyone tell me if there is a practical (not theoretical) limit on the number of connections we can achieve on SQL Server Express 2012?  We have a desktop WPF application that we intend connect to an instance of SQL Server 2012 Express installed on a Windows 2012 R2 Server.  There will be multiple users accessing the database through the WPF desktop application simultaneously. Is there a dependency on the amount of RAM installed on the server?

    Thanks,

    - Javed

    Friday, November 22, 2013 1:52 AM

Answers

  • Hello,

    your mileage will vary on the practical limit based upon the intensity of the database portion. Express edition has hard caps on CPU, Memory usage, and database size. You may find, depending on load, you can have more or less but it's going to depend on the application and how the database is being used.

    -Sean


    Sean Gallardy | Blog | Twitter

    Friday, November 22, 2013 2:04 AM

All replies

  • Hello,

    your mileage will vary on the practical limit based upon the intensity of the database portion. Express edition has hard caps on CPU, Memory usage, and database size. You may find, depending on load, you can have more or less but it's going to depend on the application and how the database is being used.

    -Sean


    Sean Gallardy | Blog | Twitter

    Friday, November 22, 2013 2:04 AM
  • HI Javed,

       I think there are no limitations on the number of connections that can be made to SQL server 2012 Express edition. However there are other limitations for CPU, MEMORY & DB SIZE etc. There is a lot of information regarding on the web. Try and google.

    Thanks,

    Bhanu

    Friday, November 22, 2013 2:11 AM
  • Hi,

    Also look at this link http://msdn.microsoft.com/en-us/library/cc645993.aspx which can be helpful.

    Thanks,

    Bhanu

    Friday, November 22, 2013 2:14 AM
  • Hi Ahmed

      In SQL Server Express user connection limit is 32,767. but before this one we should consider our hardware(Processor and memory)

      please refer the below link to restrict no of connection in SQL

       http://technet.microsoft.com/en-us/library/ms187030%28v=sql.110%29.aspx


    Thanks - SelvaKumarSubramaniam.Please MARK AS ANSWER, if my answer is useful to U.

    • Proposed as answer by Shanky_621MVP, Moderator Friday, November 22, 2013 7:30 AM
    • Marked as answer by J. Ahmad Friday, November 22, 2013 8:42 PM
    • Unmarked as answer by J. Ahmad Friday, November 22, 2013 8:44 PM
    Friday, November 22, 2013 2:24 AM
  • Thanks Sean - that makes sense.  So we will most likely need to do some continuous stress testing once the application is partly done to see if we hit any limitations. 

    - Javed

    Friday, November 22, 2013 8:34 PM
  • Javed,

    That's really the best approach. You may find that your transactions are short and there isn't too much heavy hitting logic which allows for a large number of concurrent requests. On the other hand, you may find that there are very long transactions and ad-hoc queries that are driving down connections and performance.

    -Sean


    Sean Gallardy | Blog | Twitter

    Friday, November 22, 2013 8:37 PM
  • Hi Selvakumar,

    Thanks for the reference.  It was helpful to know the upper bound and that it also depends on the application and server configurations.  Most likely we will not be imposing any limits on no of connections, as we want the maximum allowed at any given time.

    Thnaks,

    - Javed

    Friday, November 22, 2013 8:38 PM
  • Thanks for the reference, Bhanu.  I had seen that before.  Most likely we are going to see a variation based on actual application design/usage of the DB and server config.

     -Javed

    Friday, November 22, 2013 8:40 PM