Firebird Database engine has to be installed (locally on the same computer as AnterraDataCenter™) in order to extract data from either Firebird (.FDB) database files or Interbase (.GDB) database files.
Furthermore, both the Firebird ODBC driver and Firebird .NET provider have to be installed for the extraction to work. All the components are accessible through the Firebird website.
At a minimum, two separate SQL Server databases are required – one for the Sage extracted data, and one for the Extraction set up and management data. Each Management/Extraction tool combination requires its own Extraction Management database. The Sage extracted data can reside in one or more centrally located SQL databases, while the Extraction Management database(s) can reside either on the central SQL Server or on a local machine.
AnterraDataCenter supports SQL Server 2010 R2 to SQL Server 2022, including Express editions.
All SQL Server installations should be set up with the latest Microsoft SQL Server Service Packs.
Microsoft .NET Framework 4.6.2 or newer
Windows Scheduled Tasks should be set up and operational on the machine where AnterraDataCenter™ is installed if automated updates are a required feature. Scheduled Tasks are normally accessed through the control panel. AnterraDataCenter™ administrators can set up and modify scheduled tasks from within the AnterraDataCenter™ interface.
Network Configuration and Permissions
The following network configuration connections and permissions are required:
Sage Security
If Sage Security is used, you must have a valid Sage login and password available to access the data. We strongly recommend that an account be set up for the sync separate from your system admin account. We have many support calls from clients that use their system admin account. When the system admin account password is changed the sync fails.
To test whether the login and password are valid, start up and log in to Sage. Permissions within Sage itself have no impact – all logins have equal access through ODBC and are not limited by the levels of Sage Security.
Sage Data Folder
It is recommended that AnterraDataCenter™ be installed on the same computer as the Sage data server. However, it is possible to set up AnterraDataCenter™ on another computer and access the Sage Data folder(s) through a UNC connection path, but this configuration is not supported for scheduled updates. The AnterraDataCenter™ management tool can browse for this location and needs to point at the Sage file “ts.ctl”, which is located at the root of every Sage data folder. If the Sage data is not on the same computer as AnterraDataCenter™, mapped drives should not be used, as they will not be present unless a user is physically logged on to a computer. If Scheduled Tasks are used to run the extraction process, this can occur when a user is not logged on to a computer.
A minimum of read permissions is required for the user ID which AnterraDataCenter™ will be running under for the root of each Sage data folder and all subfolders.
AnterraDataCenter™ Installation Folder
Full permissions are required for the user ID which AnterraDataCenter™ will be running under, both for the Management tool and the Extraction tool.
MSSQL Service Security Account
If the SQL Server is located on a different server than AnterraDataCenter™, the MS SQL Service must be set to log on using a Domain account, rather than the Local Service account. This is necessary for the Bulk Insert process, which requires access to the share where the bulk insert temporary files are located. The domain account that is used must have permission to access this folder location. For more information on SQL Server security, please consult the following Microsoft document for SQL Server.
AnterraDataCenter will require a Shared folder, such as \\SQLServer\ADCTemp, on the SQL Server if the SQL Server is not on the same server as Sage Server. The SQL Service Account will need full read access to this folder and the Windows Account running AnterraDataCenter in Task Scheduler will need full read/write access to the Shared folder.
If the SQL Server is on the same server as Sage, then you can use a local drive such as D:\ADCTemp
Scheduled Tasks
A scheduled task to run the automatic update should be able to run under a User ID that has all of the permissions for Sage and SQL Server access as described in the above processes.
System Requirements
The system requirements for the computer running AnterraDataCenter™ are similar to the Sage System Requirements. These are as follows:
Sage 300 - Sage Construction and Real Estate
17.1 to 20.x
Operating System
- Windows 10, and Windows Server 2008, 2008 R2, 2012, 2012 R2, 2016, 2019, 2022. All in x86 as well as x64
- 2 GHz multi-core CPU minimum, 2.5+ GHz multi-core CPU is recommended
- 6GB minimum, 8GB recommended
-
Hard Disk Space:
- For the computer where AnterraDataCenter™ is installed requires approximately 100MB of disk space.
-
SQL hard drive space is roughly equivalent to the hard drive space for your Sage data. For safety, space should be at least double the immediate maximum requirement to take into account room for SQL transaction logs, indexes, and temporary files.
-
WiFi 802.11a/ac/b/g/n
-
Ethernet 100/1000MB
Pre-Installation Checklist
The following items must be performed before installing AnterraDataCenter™:
-
Microsoft .NET framework 4.6.2 or newer installed
-
Computer meets or exceeds minimum hardware System Requirements
-
Sage ODBC installed and functional.
-
SQL Server installed, configured, and functional.
-
Sage security account and password for the data sync available. Do not use the sys admin account.
-
Sage data folder location is accessible for user account which will install and run AnterraDataCenter™.
-
SQL or Integrated Security set up for user account that will administer AnterraDataCenter™
-
Scheduled Tasks functional (requires local administrator privileges)
If the SQL Server is on a different computer than AnterraDataCenter™, you must additionally check the following:
-
Share for bulk insert files set up on SQL Server which is fully accessible by the account which will be running AnterraDataCenter™
-
MS SQL Service running under a domain account with a minimum of read access to the temporary folder share, and with at least minimum security required to run SQL Server.
Fill out the following form to get a link to set up your ADC install: