AGRIS Customer Documentation

MSSQL Server and Client Configuration Recommendations and Requirements

Cultura Technologies invests in testing using the latest supportable version of Microsoft SQL with the AGRIS Product.

When specific instances or conflicts in capabilities or functionality arise, Cultura Technologies recommends to validate/confirm function in the then current MSSQL version.

MSSQL 2022

AGRIS supports MSSQL 2022 as of version 22.3.0  The specific Cumulative Update tested and supported is Update 7 or higher.

 

Standard

  1. Hardware and Software Requirements for MSSQL 2022

  2. Release Notes MSSQL 2022

  3. Whats New in MSSQL 2022

MSSQL 2019

AGRIS supports MSSQL 2019 as of version 20.1.0.  The specific Cumulative Update tested and supported is Update 4.

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

Standard

  1. Hardware and Software Requirements for MSSQL 2019

  2. Release Notes MSSQL 2019

  3. Whats New in MSSQL 2019

MSSQL 2017

AGRIS supports MSSQL 2017 as of version 18.4.0.  The specific Cumulative Update tested and supported is Update 11.

(mainstream support ended 2022)

Standard or Enterprise

  1. Hardware and Software Requirements for MSSQL 2017

  2. Release Notes MSSQL 2017

  3. Whats New in MSSQL 2017

MSSQL 2016 SP1 or Higher

(Note: MSSQL 2016 requires use of Windows Server 2012 or higher to operate)
(mainstream support ended 2021)

Standard or Enterprise (Recommended Version)

  1. Hardware and Software Requirements for MSSQL 2016 SP1

  2. Feature Pack details for MSSQL 2016 SP1

  3. Release Notes MSSQL 2016

  4. Whats New in MSSQL 2016

  5. MSSQL 2016 SP1 Server and Client Configuration Recommendations



Important

If any discrepancy exists between this table, Microsoft Sql Server end of support options or the Microsoft Product and Services Lifecycle Information page, then the Microsoft Lifecycle supersedes this table, as this table is meant to be used as an approximate reference of now available, currently supportable options.

https://learn.microsoft.com/en-us/sql/sql-server/end-of-support/sql-server-end-of-support-overview?view=sql-server-ver16#lifecycle-dates

 

Version

Release year

Mainstream Support end year

Extended Support end year

Version

Release year

Mainstream Support end year

Extended Support end year

SQL Server 2022

2022

2028

2033

SQL Server 2019

2019

2025

2030

SQL Server 2017

2017

2022

2027

SQL Server 2016

2016

2021

2026

SQL Server 2014

2014

2019

2024




MSSQL Server Recommendations for success

  • MSSQL datasets on average are 4-6 times larger than PSQL 

    • (20 user, 5 location systems should expect approximately a 10 GB production dataset)

  • All datasets are managed within the same MSSQL "Multi-Tenant" database

  • Minimum AGRIS hardware requirements will vary based on the size of your organization and datasets.   

  • Running SQL Server on a virtual machine will be slower than running natively because of the overhead of virtualization. 

  • The MSSQL database engine server should be setup and configured as a single task server, focused on MSSQL database operation.  Other applications and AGRIS should NOT be installed on the same server as the MSSQL database engine server for optimum performance. 

  • The use of Azure is not currently supported nor has testing for optimum configuration been completed for AGRIS using MSSQL.

  • The MSSQL, AGRIS Application Servers, Terminal servers should be installed and operating within the same server network and cluster for optimum performance. 

  • A test environment should be configured and reviewed by key members prior to going live with AGRIS on MSSQL to understand / ensure server and network performance is optimized for "live" use within your network.

  • Network communication speeds may impact end user experience. 

  • Review the following details for planning your install.

MSSQL Client expectations and sizing.

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

    1. The memory consumption for one AGRIS on MSSQL 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 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 on MSSQL 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 (4 cores)

      • Memory 32 GB

      • OS 64-bit Windows Server 2012 R2 Standard Edition

      • Hard Drive 1TB 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

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-6X 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.

Related articles



3820 Mansell Road, Suite 350 ✦ Alpharetta, GA 30022 ✦ www.GreenstoneSystems.com
© 2011 - 2024 Cultura Technologies LLC. All Rights Reserved Worldwide.  Products and company names mentioned herein may be trademarks or registered trademarks of their respective owners.