Versions Compared

Old Version 44

changes.mady.by.user Russell Shirley

Saved on

compared with

New Version Current

changes.mady.by.user Jon Delaney

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 Culture , 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

...

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

    • (20 user, 5 location systems should expect aprox 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.

...

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

...