Log Files Details for Threaded, Batch, Kubernetes and ACI execution

Whether running a threaded, batch, k8s or aci run, the tooling will create several log files for you reference, auditing and troubleshooting.

For a threaded run these logs will be located in the current directory or in the path designated by the --rootloggingpath argument
For a batch run the logs will be stored in the Azure Storage account associated with the Batch account. You can view the logs in several ways, including the the Azure portal, Azure Batch Explorer and Azure Storage Explorer.
For k8s runs on Kubernetes and aci runs on Azure Container Instances, the logs will be stored in Azure storage that you can access with the Azure portal or Azure Storage Explorer.

Note: For a batch run these files are consolidated logs from across all of your Batch nodes and2 individually per node in the “Task#” subfolders

Output Config Files

There will be one (or two, depending on the run success) .cfg files created - successdatabases.cfg and/or failuredatabases.cfg. These list successful targets and targets that reported a failure, respectively. Failure does not guarantee rollback: nontransactional work or changes committed before an output-persistence error may already be applied. Inspect the detailed logs before retrying. The format matches the --override argument for follow-up runs once replay is known to be safe.

Example contents for successdatabases.cfg and failuredatabases.cfg

sqllab2-b.database.windows.net:SqlBuildTest,SqlBuildTest001
sqllab2-a.database.windows.net:SqlBuildTest,SqlBuildTest006
sqllab2-b.database.windows.net:SqlBuildTest,SqlBuildTest006
sqllab2-a.database.windows.net:SqlBuildTest,SqlBuildTest001
sqllab2-b.database.windows.net:SqlBuildTest,SqlBuildTest007
sqllab2-a.database.windows.net:SqlBuildTest,SqlBuildTest007
sqllab2-a.database.windows.net:SqlBuildTest,SqlBuildTest002

High level log files

For a quick reference, three high-level log files are created: commits.log, errors.log, and SqlBuildManager.ThreadedExecution.log. The commits.log and errors.log files contain the top level success (commits) and failures (error) logs, including: time stamp, run id (a unique value for a single database build), server name, database name, and final return code for the database run (Committed, Rolled Back, etc.).

NOTE: The second column in each of the samples below is the unique “run id” for the build and can be correlated across all log files for a specific build run.

Sample contents for commits.log

[2021-06-25 12:01:26.722 ] f929636010584a68827634229c9f3b3e  sqllab2-b.database.windows.net  SqlBuildTest001: Committed
[2021-06-25 12:01:26.722 ] f929636010584a68827634229c9f3b3e  sqllab2-a.database.windows.net  SqlBuildTest006: Committed
[2021-06-25 12:01:26.722 ] f929636010584a68827634229c9f3b3e  sqllab2-b.database.windows.net  SqlBuildTest006: Committed
[2021-06-25 12:01:26.722 ] f929636010584a68827634229c9f3b3e  sqllab2-a.database.windows.net  SqlBuildTest001: Committed
[2021-06-25 12:01:28.373 ] f929636010584a68827634229c9f3b3e  sqllab2-b.database.windows.net  SqlBuildTest007: Committed
[2021-06-25 12:01:28.397 ] f929636010584a68827634229c9f3b3e  sqllab2-a.database.windows.net  SqlBuildTest007: Committed
[2021-06-25 12:01:28.413 ] f929636010584a68827634229c9f3b3e  sqllab2-a.database.windows.net  SqlBuildTest002: Committed
[2021-06-25 12:01:28.432 ] f929636010584a68827634229c9f3b3e  sqllab2-b.database.windows.net  SqlBuildTest002: Committed
[2021-06-25 12:01:29.754 ] f929636010584a68827634229c9f3b3e  sqllab2-a.database.windows.net  SqlBuildTest008: Committed

Sample contents for errors.log

[2021-06-25 11:48:57.944 ] fcf97151e8de4fcf939a43891f2b817b  sqllab2-a.database.windows.net  SqlBuildTest001: Rolled Back
[2021-06-25 11:48:57.948 ] fcf97151e8de4fcf939a43891f2b817b  sqllab2-a.database.windows.net  SqlBuildTest009: Rolled Back
[2021-06-25 11:48:57.952 ] fcf97151e8de4fcf939a43891f2b817b  sqllab2-a.database.windows.net  SqlBuildTest003: Rolled Back
[2021-06-25 11:48:57.965 ] fcf97151e8de4fcf939a43891f2b817b  sqllab2-b.database.windows.net  SqlBuildTest001: Rolled Back
[2021-06-25 11:48:58.007 ] fcf97151e8de4fcf939a43891f2b817b  sqllab2-a.database.windows.net  SqlBuildTest007: Rolled Back
[2021-06-25 11:48:58.015 ] fcf97151e8de4fcf939a43891f2b817b  sqllab2-b.database.windows.net  SqlBuildTest005: Rolled Back
[2021-06-25 11:48:58.022 ] fcf97151e8de4fcf939a43891f2b817b  sqllab2-b.database.windows.net  SqlBuildTest003: Rolled Back

The SqlBuildManager.ThreadedExecution.log file contains some additional detail specific to the concurrency and timing of each thread (Queuing up thread, Starting up thread, Thread complete) as well as some summary information on the duration and number of targets for a build.

Sample contents for SqlBuildManager.ThreadedExecution.log

[2021-06-25 12:01:31.251 ] f929636010584a68827634229c9f3b3e  sqllab2-b.database.windows.net  SqlBuildTest010: Starting up thread
[2021-06-25 12:01:31.257 ] f929636010584a68827634229c9f3b3e  sqllab2-a.database.windows.net  SqlBuildTest004: Thread complete
[2021-06-25 12:01:31.257 ] f929636010584a68827634229c9f3b3e  sqllab2-a.database.windows.net  SqlBuildTest005: Queuing up thread
[2021-06-25 12:01:31.257 ] f929636010584a68827634229c9f3b3e  sqllab2-a.database.windows.net  SqlBuildTest005: Starting up thread
[2021-06-25 12:01:31.284 ] f929636010584a68827634229c9f3b3e  sqllab2-b.database.windows.net  SqlBuildTest004: Thread complete
[2021-06-25 12:01:31.284 ] f929636010584a68827634229c9f3b3e  sqllab2-b.database.windows.net  SqlBuildTest005: Queuing up thread
[2021-06-25 12:01:31.284 ] f929636010584a68827634229c9f3b3e  sqllab2-b.database.windows.net  SqlBuildTest005: Starting up thread
[2021-06-25 12:01:33.532 ] f929636010584a68827634229c9f3b3e  sqllab2-a.database.windows.net  SqlBuildTest010: Thread complete
[2021-06-25 12:01:33.535 ] f929636010584a68827634229c9f3b3e  sqllab2-a.database.windows.net  SqlBuildTest005: Thread complete
[2021-06-25 12:01:33.541 ] f929636010584a68827634229c9f3b3e  sqllab2-b.database.windows.net  SqlBuildTest010: Thread complete
[2021-06-25 12:01:33.768 ] f929636010584a68827634229c9f3b3e  sqllab2-b.database.windows.net  SqlBuildTest005: Thread complete
[2021-06-25 12:01:33.768 ] f929636010584a68827634229c9f3b3e    : Ending threaded processing at 6/25/2021 4:01:33 PM
[2021-06-25 12:01:33.768 ] f929636010584a68827634229c9f3b3e    : Execution Duration: 00:00:09.6377429
[2021-06-25 12:01:33.768 ] f929636010584a68827634229c9f3b3e    : Total number of targets: 20

Detailed Log Files

SqlBuildManager.Console{date stamp}.log

This file contains the detailed console output. It is a capture of all of the logs that stream by in your command/console window during a build run.

“Working” folder

This is the folder that contains the runtime files such as the DACPAC, SBM and distributed database configuration files. It will also contain a sub-folder for each database server target. The folder structure is:

<server name> folders - There is one folder per target SQL Server. Within each of these is a folder for each target database.
- <database name> folders - within these folders are the following files, when applicable
  - LogFile-\<date,time\>.log - a detailed script by script run result
  - SqlSyncBuildHistory.xml - detailed log along with script meta-data (such as start/end times, file hash, status, user id)
  - SqlSyncBuildProject.xml - meta-data file for the script package run against the database
  - Error.log - full exception details when target processing fails unexpectedly

The shared SQL files remain directly under Working; they are not copied or repackaged for each database. Older runs can have <database name>Error.log directly under the server folder. Azure test diagnostics recognize both layouts and try to retrieve the detailed errors before asserting a failed command exit code, using Relay when direct storage access is network-blocked. A diagnostic-download failure is reported without replacing the original command failure.

The SQL Server AlreadyInSync Azure tests and the ACI force-custom recovery test intentionally exercise a base-script failure followed by successful DACPAC recovery. These tests require exactly four non-transient ERR entries across all worker task logs, not four per worker. Zero, one to three, or more than four entries fail the assertion. An explicit expected count also checks logs containing Custom dacpac required rather than skipping them. Existing Service Bus shutdown exclusions remain in effect, and commits, database counts, empty errors.log/per-target error logs, and no failed databases are still required. Other tests retain their existing log-validation behavior.

Worker startup logs include assembly version, console/core module IDs and the image’s source revision when available. Image build scripts pass the Git revision (with -dirty for modified source) into OCI metadata and print the ACR run ID/output image digests. For asynchronous builds, retrieve the completed run’s output images using its run ID. The ACI test runner uploads artifact-provenance.txt with its source revision and the SHA-256 hashes of the actual test/CLI/core binaries. Preserve the build receipts with test results; matching mutable tags alone do not prove that Batch, ACI and Container Apps executed the same artifact.

Troubleshooting tips

If you have SQL errors in your execution, you will probably want to figure out what happened. Here is a suggested troubleshooting path:

Open up the failuredatabases.cfg file to see what databases had problems
Taking note of the server and database name, open the server folder then the database folder
Open the logfile in the database folder. This file should contain an error message that will guide your troubleshooting should you need to correct some scripts
Inspect Error.log (or the historical <database>Error.log) for finalization/persistence failures. Verify whether changes committed before retrying: nontransactional or post-commit output failures are not evidence of rollback. Only replay failed targets after establishing it is safe.