LocalDB can be used in production on servers - Citrix uses it for the Local Host Cache on its Virtual Apps and Desktops product, and you have probably seen it if you use Azure AD Connect - but the main focus here is on the needs of the IT admin who has to deploy this software and needs to comply with regular security audits. My interest in the product is now solely as a dependency for other applications being deployed on end user devices. I did go on a SQL Server 6.5 course once and passed the SQL Server 7.0 exam in 1999 as part of my MCSE in NT 4.0, but that is a very, very long time ago. In the interests of full disclosure I am not a SQL Server expert. Finally we’ll cover deployment and configuration in an enterprise environment. Secondly, we will look at the security implications of running this software. Firstly, we’ll cover what LocalDB is, how to obtain it and how to update it. This article is pretty long, so it’s divided into three sections. What exactly is LocalDB, and how is it different from other versions of SQL Server? And, more importantly, if we have applications where LocalDB is a prerequisite, what is the best way of deploying it? If it can’t be patched, should we be deploying it? CUs and Security Updates cannot be applied manually and will not be applied via Windows Update, Windows Update for Business, or other methods.īut we’re getting ahead of ourselves. LocalDB cannot be patched beyond Service Packs. Wait, what? No security updates? From the documentation at
A cut down version of SQL Server Express intended for developers that doesn’t get security updates. SQL Server Express LocalDB is a strange offering from Microsoft.
0 kommentar(er)
