Skip to content

SQL Server

Microsoft SQL Server hosting

SQL Server licensing is provided monthly under SPLA. Installation, memory and storage settings are tuned to your workload, with backup and monitoring included.

Monthly licence model
SPLA
Low-latency data disk
NVMe
Consistent backup
Application-aware
Isolated from the app tier
Separate server

Critical settings in a SQL Server deployment

SQL Server runs with default settings, but rarely runs well with them. The most common issue is memory configuration: with no limit set, SQL Server consumes nearly all available memory and squeezes the operating system. A maximum memory value must be set relative to total server capacity.

Second is storage layout. Data files, the transaction log and tempdb contending on the same disk cause measurable slowdown in transaction-heavy systems. NVMe relieves much of that contention, but placement is still planned around the workload.

Third is backup consistency. Copying a continuously writing database at file level can produce a database that will not open when restored. Veeam's application-aware processing quiesces the database at a consistent point during capture.

Finally, access. There is no reason for a database server to be reachable from the internet. The SQL port is restricted so it is reachable only from the segment hosting the application tier.

  • Maximum memory limit set relative to server capacity
  • Data, log and tempdb placement planned for the workload
  • Application-aware consistent backup established
  • SQL port opened only to the application segment
  • Connection counts and slow queries monitored

Features

Included in the service

  • SPLA licensing

    Licensing is provided on a monthly usage model with no upfront purchase, and the edition is chosen for your workload.

  • Resource tuning

    Memory limits, parallelism and connection settings are not left at defaults but configured for the workload.

  • NVMe storage

    Data and log files run on low-latency NVMe, where the difference is clear in write-heavy operations.

  • Backup plan

    A full and daily backup calendar is established and restore scenarios are tested regularly.

  • Performance monitoring

    Connection counts, wait statistics and slow queries are tracked so bottlenecks surface early.

  • Access restriction

    The database is opened at network level only to the application tier; direct internet access stays closed.

FAQ

Frequently asked questions

Which SQL Server edition should I choose?

It depends on the features you need and your database size. Once we discuss the features you will use and your expected data volume we determine together which edition suffices; an unnecessarily higher edition brings nothing but cost.

Can I run SQL Server on the same machine as the application?

Technically possible, but we advise against it. On one machine they compete for memory and disk, and you lose the ability to scale them independently. Because traffic between separate servers runs on the 10 Gbps private network, separating them costs nothing in performance.

Can you migrate my existing database?

Yes. We first run a rehearsal migration to measure duration and surface incompatibilities, then perform the real cutover in the planned window. Data integrity verification is done with you afterwards.

Let's plan your infrastructure together

Tell us what you need and we prepare a configuration and pricing specific to you. We don't sell fixed packages; we build the deployment, licensing and backup plan with you.