US English (US)
GB English (UK)

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Create ticket
English (US)
US English (US)
GB English (UK)
  • Home
  • Install and Configure

SQL Server and Database Optimization

Written by Conrad Murray

Updated at June 20th, 2025

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Getting Started
  • FAQs
  • API Documentation
  • Integrations
  • Migration Agent
  • Directory Synchronisation
  • Remote DC agent
  • Remote Password Sync Agent
  • Install and Configure
  • Support
  • Complex Expressions
+ More

Table of Contents

Server Sizing SQL Server Memory Configuration Recovery model

Server Sizing

The recommended size for the PowerSyncPro Server depends on the number of Migration Agents reporting to it, as well as the number of objects being synchronised.

Up to 1,000 Agents and 100,000 Objects

  • 2 vCPU
  • 16 GB RAM
  • Additional 100 GB data drive
  • SQL Express can be used

Over 1,000 Agents and 100,000 objects

  • 4 vCPU
  • 32 GB RAM
  • Additional 250 GB data drive
  • Full SQL version is needed

 

SQL Server Memory Configuration

Unless otherwise configured, SQL will consume all available memory on the machine.  We would recommend setting this to half the allocated physical memory of the server.

This particular server (VM) has 16 GB RAM allocated.

Default SQL Server Memory options

We recommend setting half the physical RAM of this VM.  In this case set to 8 GB (8.192 MB)

Recovery model

From the PowerSyncProDB properties\Options we generally advise setting the Recovery model logging to Simple.  This will reduce the chances of SQL consuming too much disk space on the server.

In SQL Server, the Recovery model of a database determines how transactions are logged, whether the log is truncated automatically, and how a database can be restored.

Choosing the Right Recovery Model:

  • Simple: Use when data loss is acceptable, and you want minimal log maintenance.
  • Full: Use when data integrity is crucial, and you need point-in-time recovery.
  • Bulk-Logged: Use when bulk operations are frequent, and you can afford some data loss during those operations.

 

sql optimization database efficiency

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • How do I publish PowerSyncPro endpoints?
  • Office Applications or Outlook failing to log in after migration
  • "Is not null" and "is not empty" not working as expected.

Subscribe to Newsletter

Drop your email in the box below to sign up. We promise to keep our updates relevant and useful – and we’ll never share your details.

PowerSyncPro is the ultimate product for easing the pain and frustration during mergers, acquisitions, divestitures, and consolidations.

Terms & Conditions

  • FAQs
  • Privacy Policy
  • Cookies
  • Anti Slavery Notice

PowerSyncPro

  • Case Studies
  • Contact sales
  • Meet the Team
  • EULA

Get Connected

Room 73, Wrest House, Wrest Park, Silsoe, Bedford, England, MK45 4HR
info@powersyncpro.com

Twitter Youtube Linkedin

Knowledge Base Software powered by Helpjuice

Expand