Skip to content

Choose your language

  • No results

Choose your login

  • No results
Support
Search

Configuring Azure SQL

This page applies to:

Please note that this article discusses the setup for Azure SQL databases - not an MS SQL Server running in Azure. To configure an MS SQL database server running in Azure, please refer to the Configuring Microsoft SQL Server documentation.

To configure the Azure SQL database, perform the following tasks:

Step 1: Get the driver for the Azure SQL database

  1. For PaperCut NG/MF versions 18.3.9 and below, download the latest version of Microsoft’s JDBC driver (sqljdbc_7.0.0.0_enu.exe) for SQL Server from this link:  https://docs.microsoft.com/en-us/sql/connect/jdbc/download-microsoft-jdbc-driver-for-sql-server?view=sql-server-2017

  2. Run the downloaded file to extract the files.

  3. Copy the file mssql-jdbc-7.0.0.jre8.jar from the location the files were extracted to, to <PaperCut MF or NG install directory>\server\lib-ext\

Step 2: Create a database user

PaperCut NG/MF requires a user to connect to the database. Ensure that you have a database user set up in the Azure SQL database that has full permissions to create/drop tables and has full access to any created tables.

This user will often be created by the Azure SQL administrator when the Azure SQL database is created.

What’s next?

If you’re in the process of migrating to the external database for the first time, head over to continue with the steps (Step 5: Change the PaperCut NG/MF connection details) from our Upsize to an external database (RDBMS) article.

If you’ve already migrated (and changed the connection details as documented in Upsize to an external DB ) and are looking to confirm that the PaperCut Application Server is pointing to the external database successfully, you can check this using the system information in the PaperCut admin interface.

Navigate to the About tab > System info > Database, and you’ll see the type of database server listed. Database: Internal indicates that the App Server is still using the Internal ‘derby’ database, whereas Database: SQLServer indicates it’s using an SQL DB Server.

Comments