Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: spelling mistake


Recommended version 

MSSQL 2016 Standard or Enterprise versions - Service Pack 1 or higher  

(Note: MSSQL 2016 requires use of Server 2012 or higher to operate)

Minimum Required Version

MSSQL 2014 Standard or Enterprise R2

(Note: To enable the AGRIS AUDIT tool MSSQL 2014 Enterprise or higher is required  (Available in 2017))


MSSQL Client expectations and sizing.

  1. Greenstone has observed the following AGRIS Quantum client resource consumption in our testing environments:

    1. The memory consumption for one AGRIS Quantum client fluctuates between 128 MB and 480 MB.

    2. The memory consumption depends on the areas of the system you are running. 

    3. The highest memory consumption was observed when running large reports (100,000+ records).

    4. The memory consumption averages 240 MB when not executing large reports.

  2. The CPU load while running one client was between 1% and 4%.

  3. Peak CPU consumption was achived achieved when navigating a data grid with a large number of rows (5000+).•
  4. We have experienced a 3% increment of CPU load per additional instance of AGRIS running on the same machine performing the same operation concurrently.

Our AGRIS Quantum client testing environment is based on real hardware (non-virtualized) with the following specifications: 

      • PC Model Asus G10AC
      • Processor Intel i7 - 4770 CPU @ 3.40 GHz
      • Memory 32 GB
      • OS 64-bit Windows Server 2012
      • R2 Standard Edition
      • Hard Drive 1 TB SATA hard drive (7200 RPM)
      • Network RJ45 LAN (10/100/1000)





NOTE:  If you foresee the need to perform audits of the database, consider using MSSQL 2016 Service Pack 1 Standard/Enterprise Editions

Info

News you can use...

  • What should I expect the size per dataset to bet when migrating from PSSQL to MSSQL? Typically the database size will increase by roughly ~4-5X the current size of the pervasive files located in each dataset folder.
  • What about using MSSQL Express? In most cases, the typical AGRIS database exceeds the capacity for SQL Server Express.


Other Resources:

  1. SQL Server Storage Best Practices
  2. MSSQL Backup Best Practices
  3. MSSQL Server Maximum Capacity Specifications.

Filter by label (Content by label)
showLabelsfalse
max5
spacesACD
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel = "mssql" and type = "page" and space = "ACD"
labelsMSSQL

Page Properties
hiddentrue


Related issues