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.
“Then we wait ten minutes per build,” Marcus shrugged. mssqllocaldb
“It’s SQL Server Express,” Lena said. “Same parser, same optimizer, same transaction semantics. It just runs in my process. No Windows service. No admin rights. No installers. Microsoft shipped it with Visual Studio 2012 and it’s been there ever since, hiding in plain sight.” She dug into the Windows API
Lena’s hands trembled as she typed:
Her team, CodeCraft Dynamics, was building a complex analytics microservice. Every developer had a full SQL Server instance on their local machine. It worked fine for them. But the CI/CD pipeline, running on a clean build agent, was a barren wasteland. Installing SQL Server Developer Edition on every ephemeral build agent was like hauling a grand piano up a mountain for a single song—it took ten minutes, consumed 6 GB of disk, and failed spectacularly when two builds tried to share a single instance. “Then we wait ten minutes per build,” Marcus shrugged
Priya wrote a test that spawned 50 concurrent threads, each running a UPDATE ... OUTPUT deleted.* statement inside a SERIALIZABLE transaction. On SQLite, it would have deadlocked instantly. On LocalDB, it ran perfectly—because it was SQL Server.