Quality Products,
Excellent Service,
Reasonable Prices



In all cases there needs to be an SQL server where the database is stored. Then you will need to decide how you will run the SGA application. There are 3 options and combinations of these can be used for different workstations.

Terminal Server Installation

The SGA application is accessed through Microsoft’s remote desktop and/or remote app. It uses the resources of the server instead of their local workstations. If multiple terminal servers are required, each server will need the installation package run locally, or access through a network share. A hosted environment uses Terminal Services.

  • Any workstation with an internet connection is sufficient, even non-Windows devices such as Macs and iPads.
  • Only the terminal server(s) will need the application installed, upgraded, and maintained.
  • Workstations do not need to meet any of the system requirements.
  • You will receive the best performance if the SQL database is installed on the terminal server, and recommended specs are deployed.

  • Requires Microsoft Rdp Licenses
  • Terminal Servers have a higher risk of running into issues related to printing, scanning, graphical issues, file transfer, and security.


Shared Folder Installation

The SGA application is accessed from a shared folder on the network. It will use the local workstation’s resources, but the application and data are stored on the server. This is the least problematic installation and is most preferred for a group of workstations all on the same LAN.

  • All printing, scanning, and file browsing is done locally.
  • Installation and upgrades are in one place.

  • Does not work well for remote locations, may even be impossible depending on bandwidth limitations.
  • All workstations must meet system requirements.


Local Installation (not recommended for most installations)

The SGA application is installed on and accessed from the local workstation. The SGA package will be installed to the default path C:\Program Files\SGA, and the installation will ask to specify the SQL server and instance name to which it will connect. You should only use this method if you are a single user.

  • Single user installations will perform well.

  • The hardest to maintain for multiple user installations, troubleshooting is more difficult because of workstation variables.
  • Every workstation will need the application installed locally and every ongoing upgrade.
  • Application versions can get unsynchronized across workstations, causing crashes and other errors.
  • All workstations must meet system requirements.