Created on 01-13-2020 | Last modified on 01-21-2021

Minimum Requirements

Application Server:

  • Microsoft Windows Server 2012, Server 2012 R2, Server 2016, Server 2019
  • 32-bit or 64-bit supported
  • 1.4 GHz processor
  • 1 GB RAM
  • 2 GB RAM required for Sage Fixed Assets-Reporting add on
  • 5 GB free disk space

Database Server

Note: Sage Fixed Assets Premier requires a non-clustered stand-alone instance of SQL Server versions.

  • Microsoft SQL Server 2012, Microsoft SQL Server 2012 R2, Microsoft SQL Server 2014, Microsoft SQL Server 2016, Microsoft SQL Server 2017, Microsoft SQL Server 2019
  • Microsoft SQL Server Express 2014, Microsoft SQL Server Express 2016, Microsoft SQL Server Express 2017, Microsoft SQL Server Express 2019

Remote Access:

  • Server 2012, Server 2016 or Sever 2019 running Windows Terminal Services (Standard or Enterprise)
  • Windows 8.1, Windows 10 Build 1809 and above

Desktop Client:

  • Windows 8.1, Windows 10 Build 1809 and above•32-bit or 64-bit supported
  • 1 GHz processor
  • 1 GB RAM
  • 1.5 GB RAM if using Sage Fixed Assets-Reporting
  • 2 GB free disk space
  • 2 GB free disk space if using Sage Fixed Assets-Reporting

Recommended Configuration

  • Once the Premier Server install is complete: Ensure the SFAServ folder is shared with Change and Read permissions the Sage Fixed Asset user accounts on Sharing\Permissions and the Security tabs
  • Sage Fixed Assets Premier is supported on Microsoft SQL Server 2014 Express, Microsoft SQL Server Express 2016, Microsoft SQL Express 2017 and Microsoft SQL Express 2019.
    • Recommendation is to not have more than 50,000 assets per company when using SQL Server Express. Performance declines as assets in company increase.
  • Sage Fixed Assets applications are NOT supported in clustered SQL Server environments. A single stand-alone instance of SQL is needed to house the Sage Fixed Assets databases.
  • Connecting across a WAN (Wide Area Network), VPN (Virtual Private Network) or Wireless connection to the MS SQL server is NOT supported. While these type of connections will sometimes work, random disconnects and slow performance are common issues. Any issues connecting via any of the above methods cannot be troubleshot by Sage Fixed Assets Customer support

Note: It is recommended to connect via a Terminal Service to a Client which is Local to the MS SQL server. 

Before you begin

Note: If the Premier Databases are on a SQL 2005, Sage Fixed Assets Premier version 2018.1 or higher will be unable to connect to that server. Support for MS SQL Server 2005 ended in 4/2016 and Sage Fixed Assets have not tested with the platform since the 2016.1 release.

  1. The default collation setting of the SQL server must be set to: SQL_Latin1_General_CP1_CI_AS. If a different collation setting was selected when the SQL server was initially installed and configured it cannot be used to house the Sage Fixed Assets databases. An instance of SQL that was initially installed and configured with collation set to the default of SQL_Latin1_General_CP1_CI_AS must be used.
  2. The SQL Server must use Mixed Mode Authentication. Select Mixed Mode Authentication when installing Microsoft SQL Server. For more information about using Mixed Mode Authentication (rather than Windows Authentication Mode), please refer to your Microsoft SQL Server documentation.
  3. The Microsoft SQL Server service must be started and running before execution of the installation application or the Database Utility.