SQL Server

PhraseExpress supports Microsoft SQL Server connections to share phrases with a client-/server architecture in professional/enterprise networks.

Features

Benefits of using PhraseExpress with a SQL server compared to a serverless use:

  • Phrase changes are immediately available to all users.
  • SQL servers are designed to handle a large number of clients.
  • Multiple users can edit the phrase database simultaneously. No need to wait until a user has finished editing.
  • The client-/server architecture prevents write collisions and version conflicts.
  • Clients load the phrase contents on demand in the moment of text insertion to minimize memory consumption on the local clients.
  • The phrase database is centrally stored can be included in your existing SQL backup mechanism.

Limitations

  • If you need to share phrases over the internet or if you want to share phrases with a Mac, iOS or Android client, you would need to use cloud synchronization. Phrase sharing with the SQL Server is limited to the local network. VPN may work, but is not officially supported by us due to the potential configuration complexity.
  • Using PhraseExpress with a SQL Server is very easy, but its setup requires certain IT administration skills and is reserved for advanced users. We kindly ask for your understanding, that installation support for SQL server setups is not free-of-charge.
  • If a phrase is being triggered, the phrase is loaded from the SQL Server over the network connection, causing a small delay. For timing-critical applications such as spelling correction text replacements, you might want to use a separate local phrase file for all phrases, that shall reside in local memory for quick insertion.
  • The SQL database is not available if the network connection is interrupted.

Connect to SQL server

To connect a SQL server:
  1. Open the PhraseExpress main program window.
  2. Select the main menu command "File » Connect to a SQL server".
  3. Enter the computer name or IP address of the Windows PC running the Microsoft SQL server.
  4. Enter the SQL server TCP port (if different from the default port 1433).
  5. Enter the SQL database name (if different from the default name "phrases)".

If you don't know the SQL server connection data, you can create a configuration file in the "PhraseExpress SQL Client Manager". This file contains the connection information which can be loaded by clicking on "Load configuration file".

Troubleshooting tips

  • Make sure, that the SQL server service is running.
  • Authentication mode "SQL server and Windows authentication (mixed mode)" must be enabled in section "SQL server properties" in "Microsoft SQL Server Management Studio".
  • TCP/IP protocol must be enabled in the "Microsoft SQL Configuration Manager":

  • A static SQL server TCP port must be configured: In "Microsoft SQL Configuration Manager", right-click the TCP/IP protocol item, select "Properties" and switch to tab "IP addresses": Scroll all the way down to "IPAll" and configure a TCP port. 1433 is the default port for MS SQL servers (see Microsoft SQL Configuration Manager documentation).
  • Verify, that a firewall rule is set on the SQL server computer, to allow clients connecting to the SQL server through the configured TCP port (default is 1433).

Things to check on the Mac

  • Make sure, that SMB file sharing is enabled on the Mac under "System Preferences » Sharing » Options » Share files and folders using SMB" to allow the Mac finding the Windows computer by its computer name (see macOS help).
  • Try both, the server computer name and alternatively the IP address of the SQL server computer.
  • Open the Terminal and try pinging the server. Fix the network connection if you cannot ping the SQL server computer.

Table of Contents

    Table of Contents