I am most productive as a database developer when I have my own instance on my own machine that I can stop, start, drop and create at will. It is really not an appropriate development instance for developing and testing code that will be deployed to SQL Server. Compact Edition runs a SQL dialect, but it isn’t an edition of SQL Server. It has some similarities to SQL Server but has a very small footprint and runs in-process. There is also an edition called Compact Edition which has been deprecated but is still available. What options are there that could be used for development work? It then got more complicated, and continues to do so, with some interesting permutations coming for developers with the introduction of containers to Windows 2016 and SQL Server 2016. Other than the product itself, there was just a free developer edition. Should these be shared on one server, or distributed on a number of servers or Virtual machines? Should all development servers be of the same edition? Is it wise to rely on an internet connection to base all your development servers in the cloud, or is there a place for the traditional ‘SQL Server on the laptop’.īefore SQL Server 2005, it wasn’t hard to choose the edition that you’d use to develop with. The LocalDb edition of SQL Server was created to be the obvious edition for developers Does that idea make practical sense and what alternative advantages come the other editions for developers?ĭevelopment work will usually require a number of server instances. In this article we will look at the choices, and the decisions you need to make. There are several options to choose from, and various issues that you might need to bear in mind. Does the choice affect the tools that are used?Īs a developer, I need a SQL Server database against which I can develop and test code.What options are there that could be used for development work?.
0 kommentar(er)
