Database Server Guidance (Self-Hosted Customers)

TASS uses Microsoft SQL Server as the relational database back-end for TASS product. 

Supported Versions

More information on supported versions of technology stack components can be found in the System Requirements article.

We recommend the latest Service Packs and Cumulative Updates are installed regularly. Further information can be found in this Microsoft support article: Latest updates available for currently supported versions of SQL Server.

Configuration

The below settings must be configured as follows for TASS to function correctly:

Installation

As part of a new TASS installation, SQL Server will be installed and configured as per our recommended settings. A database account for the TASS application will be created. More information on installation can be found in the Installation and Migration Services (Self-Hosted) article.

Database naming

The database should be named in a logical manner.

The suggested naming convention is:       tass_sitename_production     tass_sitename_test.

Please endeavour to follow this naming convention wherever feasible. If there are multiple schools, name the databases in a way that is clear and not ambiguous. 

The school is responsible for informing TASS representatives on the correct database to use prior to them conducting data work.

By default, we will assume that ‘tass’ is the school’s production database requiring the data work, and ‘test’ is the school’s testing database.

Upgrades

An SQL Server instance can be upgraded to a newer major release in the following ways:

• Do it yourself: SQL Server versions can be upgraded by following the guidance published by Microsoft: Upgrade SQL Server Using the Installation Wizard.

• TASS Technical Services: TASS can assist with deploying updates (chargeable). TASS recommends this approach if you are not experienced with deploying and maintaining SQL Server. 

Do not upgrade to a major release that is not supported by TASS. 

Server Migrations

Assistance from the TASS Technical Services team is required if a database server migration is occurring. 

If TASS is performing the server migration services, SQL Server will be installed and configured as per our recommended settings, and a default maintenance plan will be created as per the guidance below.

Only a database user account for the TASS application will be created. No other user accounts will be migrated and these will need to be reconfigured manually by the customer once the migration is complete. 

More information on installation can be found in the Installation and Migration Services (Self-Hosted) article. 

Maintenance and Support

For self-hosted customers, maintenance of the database server and SQL Server instance is the responsibility of the customers. This includes backups and patching.

For cloud-hosted customers, all maintenance and support is included. Please contact TASS Technical Services if assistance is required. 

Recommended Maintenance

• Daily full database and transaction log backups. Note: for customers using Parent Lounge Payment Schedules, it is important ensure a backup is taken soon after each day's payment processing occurs. This processing happens at 4 AM daily (local time). 

• Daily transaction log truncation to prevent disks from filling.

Licensing

Self-hosted customers are responsible for providing their own SQL Server licensing. The per-core licensing model is recommended. 

Assistance with SQL Queries and Integrations

Per the TASS Helpdesk Service Level Agreement, no assistance is provided with developing or using SQL queries, or other integrations that connect directly to the database. The best way to integrate systems with TASS is using APIs. Further information on TASS APIs can be found in the TASS APIs article.