LogLocations - System Parameter

The Nodinite System Parameter LogLocations enables advanced disk volume management for SQL Server, allowing the Logging Service to distribute new Log Databases and associated files across multiple disks in a round-robin pattern. This maximizes throughput and overcomes the default SQL Server GUI limitations, which only allow DATA and LOG location settings.

Example: SQL Server Database Settings showing the default DATA, LOG, and Backup location limitations. LogLocations parameter provides advanced control beyond these GUI options.

Important

Proper disk configuration can significantly enhance performance and scalability. With LogLocations, you can allocate different file groups to specific disks, reducing contention and optimizing read/write operations.

Why This Matters for Your Business

✅ Optimized Performance – Distribute database workloads across multiple disks to reduce bottlenecks and improve read/write speeds.
✅ Scalability for Large Data Volumes – Ensure your infrastructure can handle increasing data loads without sacrificing performance.
✅ Overcome SQL Server GUI Limitations – Gain fine-grained control over where Nodinite stores its log data, beyond just DATA and LOG.
✅ Improved Resource Utilization – Allocate storage more efficiently, ensuring each disk operates at optimal capacity.
✅ Reduced Risk of Disk I/O Contention – Prevent slowdowns by spreading workloads intelligently across multiple drives.

How It Works

The LogLocations parameter allows custom placement of SQL Server files on different disk volumes for better performance and scalability. It supports structured JSON configurations to control the distribution of the following file groups within a Log Database:

Diagram: LogLocations workflow showing how the Logging Service distributes new Log Databases across multiple disks using round-robin configuration rotation.

• Data – Main database storage.
• ImageData – Stores payloads outside of the Events table to reduce fragmentation.
• Index – Optimized for clustered indexes and additional indexing.
• Primary – SQL default (not used by Nodinite).
• Log – Transaction log (recommended to run in Simple Recovery Mode).

The LastOrderDeployed field ensures a balanced distribution across multiple disk volumes, following a zero-based index. The system automatically manages the incremented recycling assignment.

Diagram: Comparison showing SQL Server's default 2-path limitation (DATA and LOG only) versus Nodinite's LogLocations feature enabling granular file group distribution across multiple disks for maximum performance.

Simple example with 1 disk to override the default SQL Path

data, index, imagedata and log are placed on the same disk H:.

{
	"Configurations": [{
		"CustomPathData": "H:\\MSSQLSERVER\\DATA\\",
		"CustomPathImagedata": "H:\\MSSQLSERVER\\DATA\\",
		"CustomPathIndex": "H:\\MSSQLSERVER\\DATA\\",
		"DefaultPath": "H:\\MSSQLSERVER\\DATA\\",
		"DefaultPathLog": "H:\\MSSQLSERVER\\LOG\\",
		"Order": 0
	}],
	"LastOrderDeployed": 0
}

Advanced example using 4 disks in 3 rotating groups

data, index and imagedata rotate over 3 disks (K:, L: and M:) and the primary and transaction log is placed on the 4th disk (N:).

Diagram: Round-robin rotation pattern showing how three configurations distribute Data, ImageData, and Index file groups across K:, L:, and M: drives while keeping Primary and Log files on N: drive. Each new Log Database cycles to the next configuration.

{
	"Configurations": [{
		"CustomPathData": "K:\\MSSQLSERVER\\DATA\\",
		"CustomPathImagedata": "L:\\MSSQLSERVER\\DATA\\",
		"CustomPathIndex": "M:\\MSSQLSERVER\\DATA\\",
		"DefaultPath": "N:\\MSSQLSERVER\\DATA\\",
		"DefaultPathLog": "N:\\MSSQLSERVER\\LOG\\",
		"Order": 0
	},
	{
		"CustomPathData": "M:\\MSSQLSERVER\\DATA\\",
		"CustomPathImagedata": "K:\\MSSQLSERVER\\DATA\\",
		"CustomPathIndex": "L:\\MSSQLSERVER\\DATA\\",
		"DefaultPath": "N:\\MSSQLSERVER\\DATA\\",
		"DefaultPathLog": "N:\\MSSQLSERVER\\LOG\\",
		"Order": 1
	},
	{
		"CustomPathData": "L:\\MSSQLSERVER\\DATA\\",
		"CustomPathImagedata": "M:\\MSSQLSERVER\\DATA\\",
		"CustomPathIndex": "K:\\MSSQLSERVER\\DATA\\",
		"DefaultPath": "N:\\MSSQLSERVER\\DATA\\",
		"DefaultPathLog": "N:\\MSSQLSERVER\\LOG\\",
		"Order": 2
	}],
	"LastOrderDeployed": 0
}

History

• The System Parameter was renamed from ImLogLocations in Nodinite version 7 ^{New 7.x}.
• This feature was introduced in Nodinite version 4 ^{New 4.3.0.26}.

Frequently asked questions

Find more solutions and answers in the Nodinite System Parameters FAQ and the Troubleshooting user guide.

How do I change the value?

Changing a value for the pre-defined System Parameters is described in the generic 'How do I change the System Parameters' article.

Screenshot: Managing the LogLocations system parameter in Nodinite v7. The JSON configuration overrides default SQL Server storage locations for new Log Databases.

Next Step

Administration

Related Topics

• Install and Update Tool