Skip to main content
SQL Server Recommendations
Joe Caffrey avatar
Written by Joe Caffrey
Updated over 5 months ago

Supported Application Versions

This database server hardware specification refers to the associated products built on or integrated with Capacity Management Suite® and is not valid if databases associated with the SQL version of the ServiceTracking® application are added to the Microsoft® SQL database server. This document outlines recommendations pertaining to the following TeleTracking application versions.

Application Name

Supported Versions

Capacity Management™ Suite

2021.08 – 2024.xx

TransferCenter™

3.2.0.17 – 2018.02.xx

Clinical Workflow™ Suite

8.1.3 – 2022.02.xx

TeleTracking Real-Time Locating System™

2020.02 – 2024.xx

Solution Architecture/Installation Types

TeleTracking’s solutions can be deployed in the following ways:

Installation Type

Description

One-Tier, Dedicated Server

Dedicated server running both the TeleTracking application and Microsoft® SQL Server. This environment is only applicable to a hospital with less than 150 beds.

Two-Tier, Two Dedicated Servers

Dedicated application server(s) running TeleTracking applications and a dedicated server running Microsoft® SQL Server.

Two-Tier, Shared SQL Server Environment

Dedicated application server(s) running TeleTracking applications with Microsoft SQL Server running in a shared enterprise database server environment. This deployment model is not supported for the Clinical Workflow™ Suite application.

Database Server Hardware Recommendations for TeleTracking® Solutions

Below are the recommended hardware specifications for optimal performance servicing one to three hospitals with a combined bed size of up to 1399 beds. For specific hardware sizing, please reference the Database Server Hardware Sizing Matrix.

Attribute

Specification

Database Servers Required

1

Architecture

64-bit Rack-mount Chassis

Operating System

Windows Server® 2016, 2017, 2019

CPU

8 cores 3.1 GHz (1333 MHz FSB)

Memory

16GB

Total Disc Space

500GB

Drive

CD-ROM drive

Network Interface

Ethernet 100/1000

Backup Device/Method

Customer provided

Proprietary Hardware Required

No

Proprietary Software Required

No


Database Server Hardware Sizing Matrix for Capacity Management Suite®

The matrix below is meant to provide a better understanding of the recommendations based on facility licensed bed size. It is important to understand that usage of the system may vary from hospital to hospital and the information below should be used as a starting benchmark. The benchmarks below also include closely integrated solutions and companion products. It should be noted that as part of implementation and ongoing support, situations may arise where TeleTracking will require SQL environment specs expanded above what is recommended in this document in order to ensure system functionality and an acceptable user experience.

Combined Number of Beds Recommended

CPU

RAM

Disk Space

1400 - 2000

8 cores

24 GB

1 TB*

2000 - 5000

24 cores

64 GB

2 TB*

>5000

48 cores

128 GB

4 TB*

* SSD recommended; non-RTLS clients can reduce hard drive specs by 50%

Microsoft® Software and Client Tools

SQL Server Versions supported

2014 SP2, 2016 SP2, 2017, 2019 CU 11 or Higher [Developer, Standard and Enterprise Editions]

Licensing

Microsoft® Per-Processor / Per-Core licensing

Client Tools

SQL Server Management Studio and all Configuration Tools must be installed on the application server. In addition, the service pack listed above must also be installed to update the client tools to the same version as the SQL server.

Microsoft® Software and Client Tools

Aspect

Recommendation

Scalability and Performance

TeleTracking recommends following Microsoft’s standards when establishing RAID-concepts and disk configurations to support Microsoft® SQL Database Servers for optimal I/O and performance.

Architecture

64-bit Disk Architecture

Virtualization

TeleTracking allows for SQL servers to operate within virtualized environments. TeleTracking recommends allocating the additional resources needed to account for the resources used to establish the virtual layer(s).

Test Databases

TeleTracking requires utilizing separate SQL instances for production and test databases to minimize the potential for production issues that may be caused by test environment activities.

High Availability and Replication

TeleTracking is not responsible for the setup or support of any of the below high availability/replication configurations and defers this responsibility to the client DBA or equivalent role with the understanding that performance may be impacted with the implementation of these replication methods.

High Availability and Replication

Description

Database Mirroring

Database mirroring can be implemented but the systems will not automatically redirect.

Failover Clustering

  • SQL Server Clustering is recommended when high-availability is required.

  • Active-Active and Active-Passive environments are allowed.

  • TeleTracking recommends the use of standard Microsoft® SQL Database Clustering being that any third-party software or hardware-based clustering may impact performance. software or hardware-based clustering may impact performance.

Replication and Mirroring

TeleTracking allows replication and mirroring but it is not required.

SQL Server High Availability and Disaster Recovery

  • TeleTracking allows for high availability to be utilized with most products.

  • When AssetTracking is integrated with XT CMS, AssetTracking cannot be part of the high availability.

SQL Server High Availability Configuration

If utilizing two different nodes for Always-On, the following configuration for the Availability Group should be used to allow the application to function if one node becomes unavailable.

Configuration

Setting

General > Connections in Primary Role

Allow All Connections for both instances

General > Readable Secondary

Read-Intent Only

Read-Only Routing > Read-Only Routing List

Origin Server should be referenced as a secondary route

Microsoft® SQL Server Specifics

Specifics

Details

Connection Protocols

Explicitly enable TCP. Remote connectivity from the TeleTracking application server is required.

SQL Browser Service

If connecting to a named instance, running SQL Browser for port resolution is recommended.

Collation

TeleTracking databases must reside within a SQL Server instance having a collation of SQL_Latin1_General_CP1_CI_AS which is case-insensitive (CI). This also excludes the use of Binary collations (BIN).

Maintenance

TeleTracking has created a SQL Best Practices document that outlines the preferred Maintenance. Please refer to the SQL Best Practices document located at here.

Microsoft® Security Specifications

Specifications

Details

SA or similar user account

System Administrator privileges are required for the installation of applications. During application installation, the application installer prompts for the sa credentials (or another set of SysAdmin credentials) for database creation and initial population.

Database Roles

The ‘XT’ role is created during installation and managed through the installer. Role has EXECUTE permissions on all stored procedure functions.

Application Login\User Accounts

The ‘XTDBUser’ login and database user is created during installation and managed through the installer. The login will be a member of the public role. The user will be a member of XT role and Db_Datareader Role.

Maintenance Login\User Accounts

The ‘XTDBMaint’ login and database user is created during installation and managed through the installer. The login will be a member of the public role. This user will be a member of the db_owner group and is used for Archiving routines required by the application.

Authentication

Mixed Mode (Windows Authentication and SQL Server Authentication) is required for the Capacity Management™ suite.


Additional Database Considerations for Integrated Solutions

On-Premise TransferCenter™ Details

The On-Premise TransferCenter™ application follows the same Microsoft® SQL specifications outlined throughout this document. Even though the On-Premise TransferCenter™ application utilizes a dedicated database - all sizing, SQL permissions, and specifications account for this additional application. In addition, the On-Premise TransferCenter™ application databases can be deployed in the same or a separate Microsoft® SQL instance from other TeleTracking™ application databases.

On-Premise TransferCenter™ SQL Server Specifics

Database and Sizing:
The On-Premise TransferCenter™ application consists of one application-specific database. The application database is initially deployed with a database size of 1GB and is expected to grow at the rate of 1GB per year.

Database Server Hardware:
The specifications below are for those clients deploying the On-Premise TransferCenter™ application on a separate Microsoft® SQL Environment from the core TeleTracking® application databases.

Specifications

Details

Database Servers Required

1

Architecture

64-bit

Operating System

Windows Server® 2016, 2019 Standard/Enterprise

CPU

Four physical/allocated CPU 2.0 GHz

Memory

16GB

Total Disc Space

100GB

Network Interface

Ethernet 100/1000

Backup Device/Method

Customer provided

Proprietary Hardware Required

No

Proprietary Software Required

No

Patch required for SQL 2016 SP1:
Cumulative Update 7 for SQL Server 2016 SP1

Reason: This patch contains a fix for this issue which causes the On-Premise TransferCenter™ application to be incompatible with previous versions of SQL 2016.

Verification:

The result when running SELECT @@VERSION should be:
Microsoft SQL Server 2016 (SP1-CU7-GDR) (KB4057119) - 13.0.4466.4 (X64) Dec 22, 2017 11:25:00 Copyright © Microsoft Corporation Standard Edition (64-bit) on Windows Server 2016 Datacenter 10.0 <X64> (Build 14393:) (Hypervisor)

Note: KB4057119 must be included in the result. Otherwise, the patch is not present on the server.

Clinical Workflow™ Suite Application Details

The Clinical Workflow™ suite application follows the same Microsoft® SQL specifications outlined throughout this document (referenced in Microsoft® Software and Client Tools, in Scalability and Performance, in High Availability and Replication, in Microsoft® SQL Server Specifics, in Maintenance, and in SQL Database Characteristics for Clinical Workflow™ Suite).

Configuration

Setting

General > Connections in Primary Role

Allow All Connections for both instances

General > Readable Secondary

Read-Intent Only

Read-Only Routing > Read-Only Routing List

Origin Server should be referenced as a secondary route

Database Server Hardware and Sizing Considerations

The specifications below are for those clients deploying the Clinical Workflow™ suite application.

SQL Server Specifics

Architecture

64-bit

Operating System

Windows Server® 2016, 2019 Standard/Enterprise

CPU

See matrix below

Memory

See matrix below

Total Disc Space

See matrix below

Network Interface

Two (2), 1 Gbps Ethernet Network Connections

Backup Device/Method

Customer provided

Proprietary Hardware Required

No

Proprietary Software Required

No

SQL Replication Support

Reporting databse must be setup as a full transactional replicaa of the production database

SQL SSRS Support

SSRS must also be installed with a supported SQL Version

Database Server Hardware Sizing Matrix for Clinical Workflow™ Suite

The matrix below is meant to provide a better understanding of the recommendations based on procedural/perioperative locations which should be used as a starting benchmark.

Procedural Locations

1-15

16-45

46-70

71-100

101-120

CPU Cores

4

4

4

6

6

GHz

2.0

2.0

2.0

2.0

2.0

RAM

4GB

6GB

8GB

12GB

16GB

x64

x

x

x

x

x

SQL Database Characteristics for Clinical Workflow™ Suite

The following statistics should be used as a starting benchmark. Being that the usage patterns at each site may vary, clients are urged to monitor these values to accurately scope the actual installation characteristics. If the Clinical Workflow™ suite application will be used with the Capacity Management™ suite and/or the TeleTracking RTLS™ solutions, the statistics below as well as the RAM listed above should be added to the Database Server Hardware Sizing Matrix for the TeleTracking XT™ Platform specifications as well as the TeleTracking Real-Time Locating System™ (TeleTracking RTLS™) Solutions Detailsspecifications.

Procedural Locations

1-15

16-45

46-70

71-100

101-120

Minimum Storage

90GB

200GB

275GB

375GB

450GB

Minimum tempdb Sizing

5GB

10GB

15GB

20GB

25GB

Database Growth (per year)

4.5GB

13.5GB

20.5GB

30GB

35.5GB

Transaction Log Sizes

1GB

3GB

4GB

5GB

6GB

Disk Reads AVG (KBps)

250

750

1000

1300

1600

Disk Writes AVG (KBps)

167.5

502.5

670

871

1072

Disk Reads MAX (KBps)

<1250

<3750

<5000

<6500

<8000

Disk Writes MAX (KBps)

<725

<2175

<2900

<3770

<4640

IOps (disk transfers per sec)

112.5

37.5

50

65

80

Avg KB per transfer (per IO)

8.75

26.25

35

45.5

56

Reporting Databases

Production and reporting databases can reside in a common SQL instance/environment for the Clinical Workflow™ suite application. The storage requirements outlined in SQL Database Characteristics for Clinical Workflow™ Suite reflect both production and reporting databases together. TeleTracking recommends, but does not require a separate SQL instance for reporting databases from the production databases.

Authentication

Windows Authentication is preferred for Clinical Workflow™ suite and uses an ODBC interface for database communication.

TeleTracking Real-Time Locating System™ (TeleTracking RTLS™) Solutions Details

The TeleTracking RTLS™ applications follow the same Microsoft® SQL specifications outlined throughout this document. To facilitate application integration, these application databases must be deployed in the same Microsoft® SQL instance as the Capacity Management™ suite databases.

Database Server Hardware and Sizing Considerations:

The specifications below are for those clients deploying the TeleTracking RTLS™ application(s).

SQL Server Specifics

Details

Architecture

64-bit

Operating System

Windows® Server 2016, 2019 Standard/Enterprise

CPU

2 Cores 3.1 GHz

Memory

12

Total Disc Space

See matrix below

Network Interface

Ethernet 100/1000

Backup Device/Method

Customer provided

Proprietary Hardware

No

Proprietary Software

No

Test Database

TeleTracking requires utilizing separate SQL instances for production and test databases to minimize the potential for production issues that may be caused by test environment activities.

SQL Database Characteristics:

The following statistics should be used as a starting benchmark. Being that the usage patterns at each site may vary, clients are urged to monitor these values to accurately scope the actual installation characteristics. To determine the final Microsoft® SQL specifications, the statistics listed for each applicable product under the appropriate device count should be combined. If the TeleTracking RTLS™ applications will be used with the Capacity Management™ suite or Clinical Workflow™ suite, these statistics should then be added to Database Server Hardware Sizing Matrix for the TeleTracking XT™ Platform specifications as well as the Database Server Hardware Sizing Matrix for Clinical Workflow™ Suite specifications. Please choose the largest tempdb size from either Database Server Hardware Sizing Matrix for Clinical Workflow™ Suite, Database Server Hardware Sizing Matrix for the TeleTracking XT™ Platform, or from the matrices below.

Total Asset Tags

0-1000

1001-3000

3001-5000

5001-7500

7501-10000

RAM (Minimum)

4GB

4GB

6GB

8GB

12GB

Minimum Storage

40GB

80GB

120GB

180GB

240GB

Minimum tempdb Sizing

10GB

12GB

15GB

20GB

30GB

Database growth (per year)

2GB

6GB

9GB

13GB

17GB

Transaction Logs

5GB

7GB

10GB

15GB

20GB

Avg Reads (KBps)

1

3

5

7.5

10

Max Reads (KBps)

3.6

10.8

18

27

36

Avg Writes (KBps)

85

255

425

637.5

850

Max Writes (KBps)

2051

10255

10255

15383

20510

Total Temp Tags

0-100

101-300

301-500

501-750

751-1000

RAM (Minimum)

4GB

4GB

6GB

8GB

10GB

Minimum Storage

55GB

105GB

160GB

230GB

320GB

Minimum tempdb Sizing

10GB

12GB

15GB

20GB

30GB

Database growth (per year)

3GB

7GB

12GB

17GB

23GB

Transaction Logs

8GB

10GB

15GB

20GB

30GB

Avg Reads (KBps)

1

3

5

7.5

10

Max Reads (KBps)

3.6

10.8

18

27

36

Avg Writes (KBps)

85

255

425

637.5

850

Max Writes (KBps)

2051

10255

10255

15383

20510

ServiceTracking® Details

The ServiceTracking® application follows the same Microsoft® SQL specifications outlined throughout this document. Even though the ServiceTracking® application utilizes a dedicated database - all sizing, SQL permissions, and specifications account for this additional application. In addition, the ServiceTracking® application databases can be deployed in the same or a separate Microsoft® SQL instance from other TeleTracking™ application databases.

ServiceTracking® SQL Server Specifics

Database and Sizing:

  • Microsoft® SQL Server® 2014, 2016, and 2017

  • The ServiceTracking® application consists of one application-specific database. The application database is initially deployed with a database size of 1GB and is expected to grow at the rate of 1GB per year.

Database Server Hardware:

  • The specifications below are for those clients deploying the ServiceTracking® application on a separate Microsoft® SQL Environment from the core TeleTracking® application databases.

Attribute

Specifications

Database Servers Required

1

Architecture

64-bit

Operating System

Windows Server® 2016

CPU

Four physical/allocated CPU 2.0 GHz

Memory

4GB

Total Disc Space

100GB

Network Interface

Ethernet 100/1000

Backup Device/Method

Customer provided

Proprietary Hardware Required

No

Proprietary Software Required

No

Did this answer your question?