Skip to content

SQL Server Configuration

Introduction

This document defines the recommended configuration for the Microsoft SQL Server machine hosting the X4D database. The SQL Server is the most critical component of an X4D deployment. Database performance directly affects tag queries, document linking, 3D model associations, reporting performance, and import and synchronization speed. Proper sizing of CPU, memory, and storage is essential to ensure stable and responsive operation.

Supported Operating Systems

The SQL Server machine must run a supported Windows Server operating system.

  • Preferred: Windows Server 2022 Standard or Datacenter
  • Supported: Windows Server 2019 Standard or Datacenter

The system should be configured with the following baseline practices:

  • High Performance power plan enabled
  • Latest Windows updates installed
  • Anti-virus exclusions for SQL data and log folders

Supported SQL Server Editions

X4D supports Microsoft SQL Server for Windows.

SQL Server Express

Supported for small projects or proof-of-concept deployments, including demonstrations and training environments.

  • Maximum database size: 10 GB per database
  • Maximum usable memory: approximately 1.4 GB
  • CPU usage limited to 1 socket or 4 cores
  • No SQL Agent for scheduled maintenance jobs

SQL Server Express is not recommended for production multi-user environments.

SQL Server Standard

Recommended for most X4D deployments. It provides larger database support, higher memory utilization, improved performance for concurrent users, and better long-term scalability.

SQL Server Enterprise

Recommended for very large datasets, multiple projects hosted on a single server, heavy reporting, advanced indexing or partitioning needs, and high-availability configurations.

Hardware Requirements

CPU

SQL Server performance benefits from both core count and clock speed.

Deployment size Recommended CPU
Small pilot or training system 8 cores
Standard production deployment 12 to 16 cores
Large enterprise deployment 24 or more cores

Higher clock speeds are generally more beneficial than extremely high core counts.

Memory

SQL Server performance is strongly influenced by available memory.

Deployment size Recommended RAM
Small environment 32 GB
Standard production deployment 64 to 128 GB
Large enterprise deployment 192 GB or higher

Insufficient memory can lead to slow query performance, increased disk reads, slower reporting, and reduced import performance.

Storage

Disk I/O is one of the most important factors for SQL Server performance. Separate physical disks are strongly recommended.

Drive Recommendation
1 - Operating System 250 to 500 GB SSD or NVMe
2 - SQL Data Files (MDF, NDF) Enterprise SSD/NVMe preferred, RAID 1 or RAID 10, 1 to 2 TB
3 - SQL Log Files (LDF) Separate physical SSD/NVMe, RAID 1, 500 GB minimum
4 - Backup and Staging 2 to 4 TB for backups, import staging, exports, and maintenance

Important storage guidance:

  • For production systems, SQL data files, logs, and the OS should not reside on the same disk
  • NVMe storage is strongly preferred over traditional SSDs
  • RAID 10 provides the best performance for large installations

Network

Category Recommendation
Minimum 1 Gbps network connection
Recommended 10 Gbps for multi-user environments

Higher network throughput improves responsiveness when multiple clients access the database and document repositories.

  • Place TempDB on fast SSD or NVMe storage
  • Configure regular database backups
  • Implement scheduled maintenance for index rebuild and statistics updates
  • Configure SQL Server memory allocation appropriately for the host
  • Monitor database growth to avoid storage saturation

Typical SQL Server Deployment Profiles

Small deployment

  • SQL Server Express, 8-core CPU, 32 GB RAM, NVMe storage

Standard production deployment

  • SQL Server Standard, 16-core CPU, 64 to 128 GB RAM, NVMe RAID storage

Large enterprise deployment

  • SQL Server Enterprise, 24 or more core CPU, 192 GB RAM or higher, enterprise NVMe storage arrays

Document purpose: sizing guidance for X4D SQL Server deployments. Adjust specifications based on data volume, number of concurrent users, reporting load, and growth expectations.