Limitations When Using SQL Express Editions as Backend for Protect

Version 3

    Description

     

    There are limitations when using SQL Express editions as backend for Protect. Unlike the full versions of SQL it lacks a concurrent workload-governor to "limit performance if the database engine receives more work than is typical of a small number of users. It does, however, have a number of technical restrictions which make it undesirable for large-scale deployments, including:

     

    For SQL Express 2005 & 2008:
    There is a maximum database size of 4 GB per database (compared to 2 GB in the former MSDE). The 4 GB limit applies per database (log files excluded); but in some scenarios users can access more data through the use of multiple interconnected databases.

    Hardware-utilization limits:
    Single physical CPU, multiple cores[2]
    1 GB of RAM (runs on any size RAM system, but uses only 1 GB)
    Absence of the SQL Server Agent service

     

    SQL Express 2008 R2 increased the size limit to 10GB per database.

    SQL Express 2012 also has a 10GB limit.

    Resolution


    A full version of SQL can greatly increase performance for users who regularly scan large numbers of machines or have a large number of agents deployed with Protect.

     

    Additional Information

     

    Refer to the following Microsoft articles for additional information on the features & limitations with SQL Express Editions:

    2012: http://msdn.microsoft.com/en-us/library/cc645993(v=SQL.110).aspx

    2008 R2: http://msdn.microsoft.com/en-us/library/cc645993(v=sql.105).aspx

    2008: http://msdn.microsoft.com/en-us/library/cc645993(v=sql.100).aspx

    2005: http://msdn.microsoft.com/en-us/library/ms345154(SQL.90).aspx