Skip to content
  • There are no suggestions because the search field is empty.

Should I run Acctivate on a shared SQL Server instance on the same computer?

Running Acctivate on a shared vs. dedicated SQL Server instance on the same computer affects performance, maintenance, and reliability.

When installing Acctivate, one key decision is whether to use a shared SQL Server instance (with other applications or databases) or a dedicated SQL Server instance just for Acctivate—even when both options are on the same machine. This choice can significantly impact system performance, ease of maintenance, and long-term reliability.
Here’s a comparison of both approaches when running on the same physical or virtual server::desktop_computer: Shared SQL Server Instance (Same Computer)
Pros:
  • No need to install or configure a second instance.
  • Uses less disk space and system memory overall.
  • Easier backup configuration if using a single instance strategy.
Cons:
  • Performance bottlenecks: Multiple applications may compete for CPU, memory, and I/O, especially during heavy Acctivate operations (like syncing or large reports).
  • Harder to isolate issues: Troubleshooting performance problems is more complex when multiple databases share the same instance.
  • Risk of conflicting settings or version dependencies from other applications.
:lock: Dedicated SQL Server Instance for Acctivate (Same Computer)
Pros:
  • Better performance isolation: Acctivate gets its own SQL resources (memory allocation, tempDB configuration, etc.).
  • Easier to tune and optimize SQL Server settings specifically for Acctivate's needs.
  • Reduces risk of conflicts from updates or changes made by other applications.
Cons:
  • Slightly higher resource usage due to a second SQL Server process running.
  • Requires more setup time and attention to configuration.
  • May require additional monitoring or backup setup.
:white_check_mark: Recommendation
If your server has adequate hardware resources (RAM, CPU, and fast storage), creating a dedicated SQL Server instance for Acctivate is generally the best practice, even when sharing the computer. It helps avoid performance surprises and makes it easier to support and scale Acctivate over time.
For SQL Server version compatibility and setup tips, check out:
 :page_facing_up: Acctivate SQL Server Requirements