Lena stared at the Azure DevOps pipeline logs, a waterfall of red text cascading down her screen. The error was always the same: “SqlException: Cannot open database "WidgetMetrics_Test" requested by the login. The login failed. Login failed for user 'NT AUTHORITY\SYSTEM'.”
“You can attach a debugger to the same process that’s running the database engine. When a test fails, you can pause both your app code and the SQL execution at the exact same clock cycle. Try doing that with a container.” mssqllocaldb
LocalDB . The quiet cousin of SQL Server. It wasn’t a service. It wasn’t a full instance. It was a Lena stared at the Azure DevOps pipeline logs,
That night, Lena dreamed in deadlocks.
“That’s not a test database,” she whispered. “That’s a scalpel.” Login failed for user 'NT AUTHORITY\SYSTEM'
Lena presented the results. She showed a graph: “Full SQL Server on build agent” – 11 minutes. “SQLite with faked queries” – 4 minutes, but 27 flaky tests. “mssqllocaldb” – 58 seconds, 100% pass rate.
She dug into the Windows API. LocalDB creates a named pipe for each instance, and the path length is limited. If a build agent’s temp folder path was too deep (e.g., C:\BuildAgent\_work\69\project\very\deep\path ), the pipe name exceeded 256 characters.