Cookie Consent by Free Privacy Policy Generator Update cookies preferences

Database Setup


Tascu requires a Microsoft SQL Server database to store all production data, this can be held on a local server, or in a cloud database.

Supported versions of SQL Server:

  • SQL Server 2012

  • SQL Server 2014

  • SQL Server 2016

Azure SQL Server


We will provide a SQL script to create the Tascus database.


Full Permissions

To implement automatic Tascus updates, it's useful to have the CREATE TABLE permissions applied - this will let the Tascus client run a database update script, creating any necessary tables within the Tascus database when needed.


Members of the db_ddladmin fixed database role can run any Data Definition Language (DDL) command in a database.

Minimum Required Permissions

If it's not permitted to use db_ddladmin, the minimum permissions users connecting to the Tascus database need the following permissions to run the Tascus client application: db_datawriter AND db_datareader:


Members of the db_datawriter fixed database role can add, delete, or change data in all user tables.


Members of the db_datareader fixed database role can read all data from all user tables and views. User objects can exist in any schema except sys and INFORMATION_SCHEMA.

If you are implementing minimum permissions, it's worth explicitly denying the CREATE TABLE permission, just in case the Tascus client tries to run a script to create a table, we've seen instances where 'ghost' tables have been created.



When Tascus starts for the first time, each station will need to define the connection to the Tascus database.

Behind the scenes, Tascus uses an SQLOLEDB connection string to connect to SQL server, using port TCP 1433

Was this article helpful?

Thanks for your feedback!