Document Details

Azacsnap Configure Database
Home / Scan #2 / Azacsnap Configure Database
Sad Tux - Windows bias detected
This page contains Windows bias

About This Page

This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
GitHub View on GitHub 📚 View on Microsoft Learn

Bias Analysis

Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation provides detailed, step-by-step Linux/Unix shell examples for SAP HANA, Oracle, and IBM Db2, but for Microsoft SQL Server, it only provides Windows-specific instructions and examples (e.g., using .\azacsnap.exe and Windows shell syntax). There are no examples or guidance for running AzAcSnap or SQL Server integration on Linux, despite SQL Server being supported on Linux. The documentation also references Windows tools and patterns (such as .exe invocation and backslash path separators) for SQL Server, and does not mention or prioritize Linux alternatives or parity for SQL Server scenarios.
Recommendations
  • Add explicit instructions and examples for configuring and using AzAcSnap with Microsoft SQL Server on Linux, including Linux shell commands and paths.
  • Provide parity in example commands for both Windows and Linux environments for SQL Server, using appropriate syntax for each (e.g., .\azacsnap.exe for Windows, ./azacsnap for Linux).
  • Mention and document any differences or requirements for SQL Server on Linux (such as service names, user permissions, and environment variables).
  • Avoid assuming Windows as the default or only environment for SQL Server; present both platforms equally, or clarify when a feature is Windows-only.
  • Where possible, use cross-platform language and avoid Windows-centric terminology (such as backslash path separators or .exe extensions) unless specifically required.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2026-01-14 00:00 #250 in_progress Biased Biased
2026-01-13 00:00 #246 completed Biased Biased
2026-01-12 00:00 #243 cancelled Biased Biased
2026-01-11 00:00 #240 completed Biased Biased
2026-01-10 00:00 #237 completed Biased Biased
2026-01-09 00:34 #234 completed Biased Biased
2026-01-08 00:53 #231 completed Biased Biased
2026-01-06 18:15 #225 cancelled Clean Clean
2025-08-17 00:01 #83 cancelled Clean Clean
2025-07-13 21:37 #48 completed Clean Clean
2025-07-09 13:09 #3 cancelled Clean Clean
2025-07-08 04:23 #2 cancelled Biased Biased

Flagged Code Snippets

# [Microsoft SQL Server](#tab/mssql)

The snapshot tools issue commands to the Microsoft SQL Server database directly to enable and disable backup mode.  

AzAcSnap connects directly to Microsoft SQL Server using the provided connect-string to issue SQL commands, such as `ALTER SERVER CONFIGURATION SET SUSPEND_FOR_SNAPSHOT_BACKUP = ON` or `ALTER SERVER CONFIGURATION SET SUSPEND_FOR_SNAPSHOT_BACKUP = OFF`.  The connect-string will determine if the installation is on the database server or a centralized "backup" server.  Typical installations of AzAcSnap would be onto the database server to ensure features such as flushing file buffers can  work as expected.  If AzAcSnap has been installed onto the database server, then be sure the user running azacsnap has the required permissions.

##### `azacsnap` user permissions

Refer to [Get started with Azure Application Consistent Snapshot tool](azacsnap-get-started.md)
The `azacsnap` user should have permissions to put Microsoft SQL Server into backup mode, and have permissions to flush I/O buffers to the volumes configured.

Configure (`.\azacsnap.exe -c configure`) with the correct values for Microsoft SQL Server and test (`.\azacsnap.exe -c test --test mssql`) azacsnap database connectivity.
Run the `azacsnap` test command