4 ms·
What's the benefit over giving a VM to a developer? What does a developer gets from setting up a SQL Server in a container that he doesn't get from setting a SQ
by cm2187 10y ago
What's the benefit over giving a VM to a developer? What does a developer gets from setting up a SQL Server in a container that he doesn't get from setting a SQL server in a VM?
- windowsworkstoo 10y agoMultiple copies of a large base db, for free...you only pay for the data when the differences start to flow in.
- cm2187 10y agoBut isn't it because of the drive level deduplication of data? Surely this is not docket specific?
- windowsworkstoo 10y agoI don't understand your question. My point is you can bake an image with the db of your choice, lets say that comes in at 50Gb. You can then run multiple instance of that image, for only 50Gb plus watever data differences are, as opposed to having to copy the full image and launch X vms (this is a scenario i am trying now, the size is much greater though, so it makes sense) I dont know of any hypervisors that let you do multiple instance of the same vm using diff disks?
- cm2187 10y agoYou can do that at the storage server level: https://technet.microsoft.com/en-us/library/hh831602(v=ws.11).aspx https://technet.microsoft.com/en-us/library/hh831602(v=ws.11...
- windowsworkstoo 10y agoRight didnt know that had found its way into standard Windows (as opposed to being a storage sapces feature or some such). In any case, its not really equivalent though, since it is only run periodically. My use case is specifically dev focused, wheras i would certainly consider data dedup on something less ephemeral
- benjaminwootton 10y agoReduced boot time, lower overhead, deployment speed, consistent environments, better resource utilisation, security, flexible isolation, better clustering options, no VMWare licensing fees, image signing workflows & a few more...
- d33 10y agoSecurity? Last time I tried, Docker messed up my firewall beyond control. Definitely not more secure than a VM.
- sqldba 10y agoSecurity will be awful. I'm an SS DBA. For one they seem to use the single known account (sa) which we disable EVERYWHERE because it's the first biggest known most common target of attack. In fact it's dangerous to use because it will lock randomly when anyone inside the company or elsewhere runs a scan and attempts a few passwords on it. Secondly SS is made to be patched. We get a new patch every single fucking month and sometimes twice a month. I spend 4 days per month simple patching SQL across half a thousand servers. This shit will never see it. Is this patchable? Not by any standard tools. Is this even discoverable? Fuck no. Nobody will know it exists. We don't do port scans - we look for known SQL services and use the SMO WMI ManagedComputer tools to identify them. This will work with neither. I've seen what developers do to their environments. Hundreds of copies of their databases. No backups (so logs grow and fill the disks and then I get called). No maintenance. Of course Express has no job scheduler so you're fucked anyway which is why I don't support it and instead move everyone onto Developer edition WHICH IS FREE. Anyone using this shit is on their own.
- UK-AL 10y agoThe image will be updated with latest patches, i don't how you would update an existing container though.
- cm2187 10y ago- Reduced boot time: I assume this is the case, and it is certainly desirable for firing up a new instance of a web server, but does that really apply to a SQL database? I can only think of marginal use cases. - lower overhead, better resource utilisation: agree - deployment speed: agree - consistent environments: a standard docker image is not adding anything over a standard VM image. - security: I am not a specialist but I doubt containers offer the same level of hardware enforced separation that VM offer - flexible isolation: what do you have in mind? - better clustering options: but the SQL server software itself is doing the clustering? Otherwise you will end up with inconsistent datasets But what I don't understand is the concept of a standard container image. That means this only applies to scenario with static data in the database? Unless this is for database sharding, where you fire up a new empty database to extend a database pool?
- netcraft 10y agoIs this actually for developers? It says > requires Windows Server 2016 - how many devs run that locally? Or is this for running this image inside of a windows server 2016 vm?
- josteink 10y ago> Is this actually for developers? It says > requires Windows Server 2016 - how many devs run that locally? It probably only needs the Windows container-feature. This was first made available in Windows Server 2016. But today, if you run Windows 10 Pro/Enterprise and have Anniversary Update installed, you should be able to enable the Windows Container-feature there as well. And that is a much more likely developer-setup.