none
Limitations of SQL Server 2008 R2 Express (Users, Connection, Database)

    Question

  • Can any one tell me what are the limitations of SQL Server 2008 R2 Express ,

    I mean, is there a limit on the
    Number of Concurrent Users ?
    Number of Connections ?
    Number of Databases ?

    Can it be used for desktop production applications ?

    Please advice, Thanks in advance ?

    Sanjay S Khed


    Sanjay khed
    Wednesday, December 15, 2010 11:11 AM

Answers

  • .... there is no limitation that SQL Server Express on number of concurrent users, connections, or databases.

    There is a limitation e.g. of 32,767 connection and 32,767 database per instance, but these limits are the same for all editions of SQL Server.


    Olaf Helper ----------- * cogito ergo sum * errare humanum est * quote erat demonstrandum * Wenn ich denke, ist das ein Fehler und das beweise ich täglich http://olafhelper.over-blog.de
    Thursday, December 16, 2010 7:06 AM

All replies

  • Hi Sanjay,

    Can any one tell me what are the limitations of SQL Server 2008 R2 Express ,

    I mean, is there a limit on the Number of Concurrent Users ?
    Number of Connections ?
    Number of Databases ?

    None of the above. The limitations of SQL Server Express are:
    - Maximum 10 GB per database.
    - Uses no more than 1 processor.
    - Uses no more than 1 GB of internal memory.

    Can it be used for desktop production applications ?

    Yes.


    Hugo Kornelis, SQL Server MVP
    My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis
    Wednesday, December 15, 2010 11:58 AM
  • Thanks Hugo,

    About the concurrent users, connections and database? 

     

    I mean,

     

    How many No of Concurrent Users can perform the operation on the database at a time ?

    How many No of Connections simultaneously to the database ?


    How many No of Databases
    can SQL Server Express R2 can hold?


    Sanjay khed
    Wednesday, December 15, 2010 12:17 PM
  • Hello Sanjay,

    for details see Features Supported by the Editions of SQL Server 2008 R2 and Maximum Capacity Specifications for SQL Server


    Olaf Helper ----------- * cogito ergo sum * errare humanum est * quote erat demonstrandum * Wenn ich denke, ist das ein Fehler und das beweise ich täglich http://olafhelper.over-blog.de
    Wednesday, December 15, 2010 12:35 PM
  • Hi Sanjay,

    About the concurrent users, connections and database? 

    As I already wrote in my previous reply, there is no limitation that
    SQL Server Express on number of concurrent users, connections, or
    databases.

    Of course, the limitation of 1GB RAM use and 1 processor use will
    result in performance getting slow once a threshold of concurrent
    users / connections is reached. But it's not possible to give a
    number, as this also depends on workload - thousands of users hitting
    the DB once a minute for a very simple query will not be a problem,
    but ten users doing heavy number crunching can bring even a server
    with more RAM and more processors to its knees.


    Hugo Kornelis, SQL Server MVP
    My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis
    Thursday, December 16, 2010 12:34 AM
  • .... there is no limitation that SQL Server Express on number of concurrent users, connections, or databases.

    There is a limitation e.g. of 32,767 connection and 32,767 database per instance, but these limits are the same for all editions of SQL Server.


    Olaf Helper ----------- * cogito ergo sum * errare humanum est * quote erat demonstrandum * Wenn ich denke, ist das ein Fehler und das beweise ich täglich http://olafhelper.over-blog.de
    Thursday, December 16, 2010 7:06 AM
  • Thanks Olaf,  

    “but these limits are the same for all editions of SQL Server.”  

    Actually, I am looking of the above statement.

    so far I did not find any where this is documented

    Thanks once again

     


    Sanjay khed
    Thursday, December 16, 2010 12:02 PM
  • That is true,

    Thanks Hugo


    Sanjay khed
    Thursday, December 16, 2010 12:05 PM
  • That is ture

    Thanks Hugo

     

     

     


    Sanjay khed
    Thursday, December 16, 2010 12:05 PM
  • “but these limits are the same for all editions of SQL Server.” 

    Actually, I am looking of the above statement.

    so far I did not find any where this is documented

    http://msdn.microsoft.com/en-us/library/ms143432.aspx


    Hugo Kornelis, SQL Server MVP
    My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis
    Thursday, December 16, 2010 8:31 PM
  • - Uses no more than 1 processor.

    - Uses no more than 1 GB of internal memory.

    Hugo Kornelis, SQL Server MVP
    My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis

    Do you possibly know if this limit is "per database" or "per database server" ? For example, will having 8 databases limit the sql server to use 1 gb per database with maximum 8gb for the sql server process?

    Thank you,

    Norbert

    Saturday, August 13, 2011 12:07 PM
  • hi,

    - Uses no more than 1 processor.

    - Uses no more than 1 GB of internal memory.

    Hugo Kornelis, SQL Server MVP
    My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis

    Do you possibly know if this limit is "per database" or "per database server" ? For example, will having 8 databases limit the sql server to use 1 gb per database with maximum 8gb for the sql server process?

    the "limits" are "per instance"... so "... will having 8 databases limit the sql server to use 1 gb per database ..." is false, the limit is of about 1gb for "all databases"... actually this sentence is wrong as more than the database itself goes into RAM... query plans, buffer caches, network buffers, connections structure and more go into RAM... whenever the instance goes into internal memory pressure, it will eventually release memory pages... that means that, if you "have" all your dbs (8gb) into ram, only part of them can actually be there, and all the exceeding parts have been already released... if you re-require the "data", it will not be in RAM and the storage engine is committed to perform other I/O operations to get the data in memory, thus releasing other "stuff" (again, memory pages, query plans, ...) as limited to that 1gb per edition limit... regards
    http://www.asql.biz - DbaMgr2k - DbaMgr and further SQL Tools http://www.hotelsole.com/
    Sunday, August 14, 2011 1:09 AM
    Moderator
  • Hi all,

    Is there any restriction (different from database size limit) if I want to restore a 2008 R2 backup from the Enterprise edition into an Express edition (2008 R2 too)?

    Thank you beforehand.

    Friday, September 14, 2012 3:51 PM
  • hi,

    - Uses no more than 1 processor.

    - Uses no more than 1 GB of internal memory.

    Hugo Kornelis, SQL Server MVP
    My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis

    Do you possibly know if this limit is "per database" or "per database server" ? For example, will having 8 databases limit the sql server to use 1 gb per database with maximum 8gb for the sql server process?

    the "limits" are "per instance"... so "... will having 8 databases limit the sql server to use 1 gb per database ..." is false, the limit is of about 1gb for "all databases"... actually this sentence is wrong as more than the database itself goes into RAM... query plans, buffer caches, network buffers, connections structure and more go into RAM... whenever the instance goes into internal memory pressure, it will eventually release memory pages... that means that, if you "have" all your dbs (8gb) into ram, only part of them can actually be there, and all the exceeding parts have been already released... if you re-require the "data", it will not be in RAM and the storage engine is committed to perform other I/O operations to get the data in memory, thus releasing other "stuff" (again, memory pages, query plans, ...) as limited to that 1gb per edition limit... regards
    http://www.asql.biz - DbaMgr2k - DbaMgr and further SQL Tools http://www.hotelsole.com/
    Well answered. Thanks.
    Friday, October 12, 2012 5:47 AM