To ensure that users can perform their duties well and Transpas keeps performing optimally, we have the following hardware advice.
When the hardware doesn't meet the requirements in this advice Art Systems can't guarantee that Transpas will keep performing well.
Questions about this advice? Contact us.
Because all calculations in Transpas are executed on the server, all lag on the server will directly lead to lag effects for the users.
Our advice is to use a dedicated SQL server which is only used for Transpas, so that there are no other programs that use the resources of the SQL server.
For this server we advice the following:
| CPU | 1 Quadcore, moderne top-line CPU per 10 users | |
| OS | Up-to-date, modern Windows Server | |
| DBMS | Microsoft SQL Server 2022 | Collation: Latin1_General_CI_AS or Danish_Norwegian_CI_AS |
| RAM | 16 GB + 1 GB per 2 users | No dynamic memory / memory ballooning |
| Disk | SSD | |
| Network | 1 Gbit/s |
The collation of the instance must be Latin1_General_CI_AS or Danish_Norwegian_CI_AS.
Note: not SQL_Latin1_General_CP1_CI_AS
To set this collation, click Customize on the Collation tab when installing the SQL Server.
Here, select Latin1_General as Collation designator and only check the box Accent-sensitive.
For Transpas Enterprise at least SQL Server Standard must be used. SQL Server Express is not supported.
This has to do with several limitations, including the maximum database size of 10 GB and limitation of the number of CPU cores and memory.
When using Transpas CS, SQL Express may be selected if the AS Transpas and AS Transpas History databases are still significantly below 10 GB.
Your hardware vendor should advise you on the correct licensing model for Microsoft SQL Server because it is linked with the number of processors used, or the total number of end users, including those of any other software that uses the same SQL Server license.
Transpas does not support SQL Server Replication. This causes issues during updates of Transpas.
Many servers nowadays are hosted as virtual machine. It is of course possible to host Transpas in a virtual machine, however hardware should be dedicated to the virtual machine.
CPU
We strongly advise against over-allocation of CPU cores. A CPU core can only execute 1 thing at a time. When virtual machines are assigned more CPU cores in total than the host has, the hypervisor cores must switch between the virtual machines to be executed. While executing another virtual machine, the SQL Server virtual machine (partially) stops.[1]
This causes latency and performance problems in Transpas.
RAM
In addition, memory may not be allocated dynamically. The working memory must be permanently allocated to the virtual machine. SQL Server needs quite a bit of RAM for normal operation. When restarting the virtual machine, it may take a while before it has taken up all the memory needed for normal use. With dynamic allocation, SQL Server will think that there is less memory available and therefore take up less. This leads to performance problems in Transpas.
It is possible to host the Transpas server in the cloud, and there are quite a few of our customers who do this as well. However, it is good to keep a few things in mind when doing so.
The data transfer between the client and server is significant. For the program to function properly it is therefore essential that fast data transfer is possible between the client and server.
In addition, Transpas' logic takes place almost entirely on the server. So virtually all operations involve executing code on the server and waiting for the result. A low latency between the client and server is therefore also essential.
When hosting Transpas in the cloud, we therefore always recommend combining this with a remote/virtual desktop environment in the cloud, with the same provider.
We strongly advise against local clients in combination with a server in the cloud!
Transpas does not support Azure Managed SQL instances.
To read and write files, it is necessary that the SQL Server instance is in the same domain as the workstations.
This means that the files can be accessed by all users and by the SQL Server using the same UNC path.
Experience shows that a Managed SQL instance cannot (easily) be placed in the same domain.
Offering Transpas as a remote app is not supported.
Transpas uses a link to the file system in several ways.
With a remote app, such a link is opened from the context of the machine on which the remote app is running.
As a result, it is not possible for a user to select the files on his own machine.
Drag and drop functionality is also used in various places within Transpas.
This also does not work properly via a remote app.
The use of (Azure) Blob Storage for storing files that Transpas works with is not supported.
Specifically the automated importing and exporting of files from a Blob Storage can lead to instability.
In order to implement functionality, install updates, and provide support, we must be able to log in to the Transpas server at all times.
Contact us for our preferences regarding access.
When antivirus software is installed on the SQL Server, the SQL Server processes should be excluded.
Configure antivirus software to work with SQL Server
| CPU | 1 Quadcore, moderne top-line CPU per 4 users |
| OS | Up-to-date, modern Windows Server |
| RAM | 32 GB + 2 GB per user |
| Disks | 15.000 rpm SAS of SSD |
| Network | 1 Gigabit |
| CPU | i5 – i7 |
| OS | Modern, up-to-date Windows OS |
| RAM | 8 GB+ |
| Graphics advice | Multiple monitor support |
| Browser | Latest versions of Edge, FireFox, Safari, Chrome. Chrome is the fastest. |
| JavaScript | Enabled in trusted zone |
| Internet | Broadband |