About using Microsoft SQL Server with Nodinite
Unlock the full potential of Nodinite by choosing the right Microsoft SQL Server configuration. This page details supported versions, editions, prerequisites, and best practices to ensure optimal performance, security, and scalability for your monitoring and logging needs.
✅ Supports a wide range of SQL Server versions and editions
✅ Clear prerequisites for seamless installation and upgrades
✅ Best practices for security, performance, and backup
✅ Guidance for high availability, clustering, and cloud options
On this page, you will learn about some important prerequisites and options for installing and using Nodinite with Microsoft SQL Server.
SQL Server Versions and Editions
Nodinite supports a broad range of Microsoft SQL Server versions and editions, including Enterprise, Standard, and Express. Choose the edition that matches your business needs and expected data volume.
- SQL Express is supported
- SQL Server Managed Instance (Azure) is supported
- Azure SQL Databases are currently NOT supported
| SQL Server Version | Always On support | Cluster support | Stand alone | Nodinite Version |
|---|---|---|---|---|
| SQL Server Managed Instance (Azure) | >=6.1 | |||
| 2022 | ✅ | ✅ | ✅ | ->6 |
| 2019 | ✅ | ✅ | ✅ | ->6 |
| 2017 | ✅ | ✅ | ✅ | ->6 |
| 2016 | ✅ | ✅ | ✅ | ->6 |
| 2014 | ❌ | ✅ | ✅ | ->6 |
| 2012 | ❌ | ✅ | ✅ | ->6 |
| 2008 R2 | ❌ | ✅ | ✅ | ->5.4 |
Developers can use the Developer edition for non-production environments.
If you require Logging Service, you will almost always need the Enterprise or Standard edition for sufficient capacity and features.
| Enterprise | Standard | Express | |
|---|---|---|---|
| Maximum Database Size | 524 PB | 524 PB | 10 GB |
| CPUs/Cores | OS Max | 4 sockets or 24 cores | 1 socket or 4 cores |
| Max Memory | OS Max | 128 GB | 1.4 GB |
| SQL Profiler | ✅ | ✅ | ❌ |
SQL Server Always On
For high availability, Nodinite supports SQL Server Always On. Review the About SQL Server Always On Availability Groups guide for detailed configuration steps and recommendations.
SQL Express
SQL Express is supported but has limitations. It is generally not recommended for environments with Logging Service. If you use Nodinite only for documentation and Monitoring, SQL Server Express may suffice.
| SQL Server Version | Always On support | Cluster support | Stand alone | Nodinite Version |
|---|---|---|---|---|
| 2022 | ❌ | ❌ | ✅ | -> 6 |
| 2019 | ❌ | ❌ | ✅ | -> 6 |
| 2017 | ❌ | ❌ | ✅ | -> 6 |
| 2016 | ❌ | ❌ | ✅ | -> 6 |
| 2014 | ❌ | ❌ | ✅ | -> 6 |
| 2012 | ❌ | ❌ | ✅ | -> 6 |
| 2008 R2 | ❌ | ❌ | ✅ | ->5.4 |
Warning
The 10 GB limit for SQL Express makes it a poor choice for logging scenarios.
Tip
SQL Express 2019 and later can be upgraded to Standard edition, allowing you to start small and scale as your business grows.
Installation Path
If Nodinite is not installed on the same Windows Server as SQL Server, you can install SQL Server in any folder. For multi-server environments, review System Parameters and the SqlPackageExecutable user guide for configuration examples.
Collation
Nodinite requires a SQL Server instance with a collation of type CI_AS (Case Insensitive, Accents Sensitive). Choose a collation that matches your language, policy, and business requirements.
Learn more about SQL Server Collations in the official documentation.
Security
Security is critical for your SQL Server environment. Follow these best practices:
Account for SQL Server Instance
Run the SQL Server instance with an AD service account (not a local account) to ensure proper SPN registration in Active Directory. This is required for Kerberos authentication and secure delegation. See Trusted for delegation.
Kerberos
Kerberos is enforced by Windows and is essential for secure, multi-server environments. Ensure the following are properly configured:
- SPNs
- Trusted for delegation
- Firewalls
- Authentication and Authorization
Trusted for delegation
See the Trusted for delegation user guide for details.
SPN
When Nodinite uses a Linked Server, the SQL Server instance(s) must have its Service Principal Name (SPN) properly registered. See Account for SQL Server Instance for more information.
Linked Server
Review the Linked Servers section for configuration guidance.
DTC
See the Transactions MSDTC user guide.
Note
The type of DTC configuration varies with your SQL Server setup and organizational policies.
Performance optimizations
Maximize your Nodinite experience by following these performance tips:
- Run Nodinite in dedicated SQL instances to guarantee resources and simplify troubleshooting
- Assign dedicated disk volumes for the Log Databases using the LogLocations system parameter
- Keep the Logging Service close to the SQL Server hosting the Log Databases
- Repeat these optimizations on ALL SQL Server instances (including BizTalk Server databases)
- Use -T1118 Trace flag on SQL Instances (<2016) to optimize TEMPDB
- Disable PAC Verification if your policy allows, to reduce RPC calls and improve performance
- Install Nodinite on machines with dedicated swap volumes (>2.5x physical RAM) and SQL disks with >300 MB/s R/W
- Ensure a secure backup volume or network share with enough free space for Nodinite databases
- Windows Servers hosting Core Services should have at least 16GB RAM; high-volume environments may need more
- Use Simple recovery mode for Log Databases with BizTalk Server to boost performance
TempDB optimization
- For each core (up to 8), create 1 tempdb file of at least 128 MB (no auto growth)
For example, with 14 cores, use 8 tempdb files. Placing tempdb files on different volumes can further improve performance.
Backups
Nodinite databases are critical for your monitoring and logging operations. Follow these best practices to ensure data integrity and availability:
- DO NOT LOSE ANY DATA OR CONFIGURATION!
Important
Make sure to backup all your Nodinite databases, and make sure the documentation for the restore operation is available to the appropriate stakeholders