When this happens, the next request(s) will most likely have poor performance and could even get a timeout. Despite having the same performances of a regular SQL Server Express instance - since they share the same database engine - the LocalDb underlying process will shut down itself if it doesn't have any request for a while.The reasons for that are fairly simple to explain and understand: We briefly talked about it in a couple posts some months ago, such as when we compared the Entity Framework Data Modeling patterns (Code-first, Model-first and Database-first) and in our ASP.NET MVC 5 Web Application Project Setup Guide.Īlthough LocalDB proved itself to be a great development choice, it's not a good idea to use it in a production environment of any kind. NET developer working with Visual Studio, you'll most likely know SQL Server LocalDB: a specialized edition of the well-known Microsoft SQL Server engine - firstly introduced in SQL Server Express 2012 - acting as a minimal, on-demand, version of SQL Server designed for application developers. Since its first introduction LocalDB has proved itself to be a great development tool, especially when used as an 'embedded database' to quickly test our Data Model without having to setup a whole DBMS service. Installing SQL Server Management Studio.

Visual studio 2017 sql server localdb