"I can't keep doing this," she muttered, watching her battery drain from 100% to 60% in fifteen minutes.
She closed the lid and went home at 4:59 PM. microsoft sql server express localdb
She ran integration tests. They ran in 800ms. She ran unit tests with a fresh database. sqllocaldb stop Contoso followed by sqllocaldb delete Contoso wiped everything clean in a millisecond. "I can't keep doing this," she muttered, watching
"There isn't one," Marcus said. "It spins up on-demand. When you close your app, it goes to sleep. It's a SQL Server engine that weighs less than a paperclip." That night, Sarah refactored everything. They ran in 800ms
Sarah wrote on her blog that night: "SQL Server Express LocalDB is the unsung hero of .NET development. It’s the full power of SQL Server without the ceremony. No services. No permissions. No 'I forgot the sa password.' Just (localdb)\MSSQLLocalDB and a smile." She looked at her task manager. 0% CPU. 3.2GB RAM free. Her laptop fan was silent.
LocalDB wasn't a toy. It was a full —with the same TRANCOUNT , the same sp_who2 , the same transaction isolation levels—but wearing a stealth suit. It ran as a child process of her application. It communicated over named pipes , not TCP/IP (though you could enable that). It even supported multiple instances : one for development, one for testing, one for that legacy reporting tool she was scared to touch.