localdb in sql server 2014 developer edition

All developers should have a local instance of SQL Server AND a shared SQL server instance. I guess one of the biggest concerns would be the ability for local db instances coming out of date, but thats a software management issue, not a DBA one IMO. Backups from 'production' third party systems being restored and truncated where appropriate for validation and developmentĬan anyone see any issues? Am I missing something?.Scripts that created the database being generated for deployment to production.Now, assuming it's ONLY for development, and the database will not be 'moved' to production and the only movements would be: Only SharePoint and SCCM have issues around this as far as I know ) To me all these arguments are particularly invalid, with perhaps the exception of the patching ones but if a database on a local machine is purely used for development activities, and not testing, then the patching would be proven out when an application progressed through Test / UAT etc to Production.Ĭollation does not appear to be a valid reason, as if this was a concern for the database it should be set when it's created anyway. Collation differences that can cause problems when moved to production.Recoverability data is recoverable and still backed up.Data security only data on the development servers gets used for development.Ability to prove and validate any patches on the above.Patch level consistency between development servers and production.Many companies prevent developers from install SQL Server Express and the like on development machines, instead promoting the use of centralised development SQL Servers. Much like the vein of the question that was posted here previously around ' Should developers be able to query production databases?' I wanted to get your thoughts on another particularly annoying topic!

Localdb in sql server 2014 developer edition