Теперь SQL Server 2014 Developer Edition является бесплатной версией SQL Server, которую вы можете скачать по ссылке. Данная редакция SQL Server обладает функционалом Enterprise Edition, но её нельзя использовать на продуктивных системах. Основное назначение данной редакции это тестирование и разработка.
Когда выйдет SQL Server 2016 Developer Edition она так же будет бесплатной.
Будьте внимательны, лицензия на операционную систему всё равно требуется.
- Aaron Bertrand
- Visual Studio Dev Essentials is FREE
- Evaluation Edition has a secret
- MSDN is, well, MSDN
- There is a «Statue of Liberty» play
- And about that free lunch.
- There’s also a Disclaimer
- Why use SQL Server in containers?
- Pulling and Running SQL Server 2016 in a Windows Container
- Connecting to SQL Server 2016
- SQL 2016 Features Supported on Windows Server Core
- Further Reading
Published On: July 15, 2016
Back in March, Microsoft gleefully announced that Developer Edition would now be free. But in that time, I’ve seen plenty of confusion around where to get it. More specifically, where to get it with no strings attached, including questions like, «Can I just buy it so I don’t have to sign up for ?»
The simple answer is no — there is no free lunch. The three supported methods I know of to obtain SQL Server 2016 Developer Edition all involve either registering or paying. This isn’t a bad thing, IMHO; you and I have both given up our e-mail addresses in exchange for things far less valuable than a used-to-be-$49-or-$59 piece of software. But read on, as there is a fourth option that might be more palatable.
Visual Studio Dev Essentials is FREE
THE CATCH: You have to sign up.
If you go to this URL , you will see this screen:
Click Join Now , and you’ll be offered three options: to sign in with your work or school account (you may already have access to Visual Studio Dev Essentials), to sign in with your Microsoft account (hotmail/outlook), or to create a new Microsoft account (which you can do if you just want to create a throwaway account for this):
You’ll arrive on a screen with a bunch of tiles, including this one, below left. When you click «Download» you will be asked to confirm the prompt, below right. Then you’ll need to click «Download» again.
(This screen will also offer ISOs of SQL Server 2014 Developer Edition. And note that the link to the KB at the bottom is currently incorrect; it should be KB 3164398.)
A few people have objected to signing up for Dev Essentials, but in addition to providing ready access to SQL Server 2016, there are a bunch of other benefits too, such as free access to PluralSight. This route really shouldn’t be dismissed, IMHO — again, other than giving up an e-mail address, there’s nothing to lose.
Evaluation Edition has a secret
THE CATCH: You have to register.
Go to the TechNet Evaluation Center, where you will see this prompt:
Go ahead and register (use a junk e-mail address if you want), and don’t worry, I’ll explain why this disclaimer won’t come into play:
When you click Continue, you will be prompted to download the file SQLServer2016-SSEI-Eval.exe . This is the new basic installer they blogged about recently. Yes, that file name looks alarmingly like the Evaluation Edition of SQL Server, but bear with me. Once it’s downloaded, run it, and choose Custom on this screen (the Basic option is the real sweet spot of this new basic installer, but we’re not going to use that option today):
Next, you’ll tell installation where to put the files it’ll need to download, and then click Install (don’t worry, this isn’t going to start an actual install yet):
Now you’ll be stuck on this screen for a while (especially if you’re on hotel broadband, like I am):
This will create a folder called Evaluation , in the chosen media location, and download the ISO contents there. They’ll already be extracted, so you can run setup without having to mount an ISO (if you want an ISO instead, choose Download Media instead; further information about that path can be found down below). Inside that is the traditional Installation Center you’re probably already very familiar with, and the installer should launch that after the download finishes. If not, just navigate to the folder manually, and run SETUP.EXE. Then choose «Installation» > «New SQL Server stand-alone installation or add features to an existing installation» and proceed through setup as you usually do. On the «Installation Type» screen, choose «Perform a new instance of SQL Server 2016.» On the next screen is where the magic happens:
Yes, even though you’ve registered for Evaluation Edition, you have a choice between that, Express, and Developer. People are skeptical about this, but the ISO is not tied to any specific edition; it is capable of installing any edition, depending on the product key entered, or your selection here.
MSDN is, well, MSDN
THE CATCH: You have to pay.
If you have MSDN already (check with your employer or educational institution), this is pretty easy. Just go to Subscriber Downloads, click on SQL Server 2016, and the Developer Edition ISO will be one of the options:
(I’ve included all the relevant MSDN subscriptions to hopefully make it easier to determine if you are eligible. And again, please note that the link at the bottom is wrong; it should point to KB 3164398.)
There is a «Statue of Liberty» play
THE CATCH: Unsupported/Undocumented/May Change.
When you build a web installer that puts a fancy interface around calls to URIs, it’s hard to really keep those URIs secret. I’ve seen people already point out that you can download the Dev-specific basic installer from the following URL, without having to sign up or register for anything:
http://go.microsoft.com/fwlink/?Link >Now, keep in mind, that fwlink may change, especially if they roll future CUs/SPs into the package, and the GUID-based URL behind it may change also. But for now this seems to be a bit of a back door — it downloads the new simple installer for Developer Edition ( SQLServer2016-SSEI-Dev.exe ), and then the process is identical to the Eval Edition steps above, except that things are labeled Developer instead of Evaluation. But just to do something slightly different, let’s choose Download on that initial screen instead of Custom:
Now you’ll have a couple of additional settings to configure:
And when you click Download , you will be waiting on this screen for a bit:
When it’s complete, you will find an ISO file ( SQLServer2016-x64-ENU-Dev.iso , not the extracted contents), which you can mount and run setup from. If you want the extracted setup files instead of an ISO, stick with the approach using the Custom option I described above.
And about that free lunch.
An e-mail address is a small price to pay for Developer Edition. But for anyone using any of the free editions of SQL Server 2016, you’re already giving up something else to get it: telemetry data. As you can read about in KB #3153756, Connect #2775205, and a Brent Ozar blog post, the collection of feature usage data has switched from a default of opt-out in previous versions to a default of opt-in in SQL Server 2016. Further, they have made it a bit harder for users of the free editions (Evaluation, Developer, and Express) to turn off this phone-home functionality (I show how in a post back in April). I suspect most users of these free editions either won’t notice this change (which is why folks like Brent and I try to beat the drums about it), or will notice but won’t go to the effort to disable it. My fear is not that private data will be transmitted to Microsoft and they will use it in some nefarious way, but rather that someone with HIPAA or similar constraints will inadvertently go out of compliance, and I don’t even fully comprehend the potential scope of consequences there.
There’s also a Disclaimer
Note that the ISO you ultimately get, whether it is extracted or not, is RTM, so it does not have the GDR fix from KB #3164398, and it won’t be updated with any CUs, either. They usually only post new downloads to MSDN when they have built a fresh ISO with a new service pack slipstreamed, though I don’t know how that will change with their frequent changes to the servicing model and release strategy. Please use the check for updates feature during setup, regardless of which approach you take.
We are excited to announce the public availability of SQL Server 2016 SP1 Developer Edition in Windows Containers! The image is now available on Docker Hub and the build scripts are hosted on our GitHub repository. This image can be used in both Windows Server Containers as well as Hyper-V Containers.
We hope you will find this image useful and leverage it for your container-based applications!
Why use SQL Server in containers?
SQL Server 2016 in a Windows container would be ideal when you want to:
- Quickly create and start a set of SQL Server instances for development or testing.
- Maximize density in test or production environments, especially in microservice architectures.
- Isolate and control applications in a multi-tenant infrastructure.
Before you can get started with the SQL Server 2016 Developer Edition image, you’ll need a Windows Server 2016 or Windows 10 host with the latest updates, the Windows Container feature enabled, and the Docker engine.
Pulling and Running SQL Server 2016 in a Windows Container
Below are the Docker pull and run commands for running SQL Server 2016 Developer instance in a Windows Container. Make sure that the mandatory sa_password environment variable meets the SQL Server 2016 Password Complexity requirements.
First, pull the image
Then, run a SQL Server container
• Running a Windows Server Container (Windows Server 2016 only)
• Running a Hyper-V Container (Windows Server 2016 or Windows 10)
Connecting to SQL Server 2016
From within the container
One of the ways to connect to the SQL Server instance from inside the container is by using the sqlcmd utility.
First, use the docker ps command to get the container ID that you want to connect to and use it to replace the parameter placeholder “DOCKER_CONTAINER_ID” in the commands below. You can use the docker exec -it command to create an interactive command prompt that will execute commands inside of the container by using either Windows or SQL Authentication.
• Windows authentication using container administrator account
• SQL authentication using the system administrator (SA) account
From outside the container
One of the ways to access SQL Server 2016 from outside the container is by installing SQL Server Management Studio (SSMS). You can install and use SSMS either on the host or on another machine that can remotely connect to the host. Please follow this blog post for detailed instructions on connecting to a SQL Server 2016 Windows Containers via SSMS.
SQL 2016 Features Supported on Windows Server Core
Please refer to this link for all SQL Server 2016 features that are supported on a Windows Server Core installation.
Please give the SQL Server 2016 Developer image a try, and let us know what you think!