Hacker News new | ask | show | jobs
by ashtavakra 3534 days ago
All this is nice, but once the SQL Server database crosses a certain size, there are things one needs to do like separating transaction logs, data files, tempdb files to separate disks for acceptable performance. I am not sure how that will work with SQL Server inside a container.
4 comments
karma_fountain 3534 days ago
Good for development environments though. Probably don't want to be running SQL Express for large databases anyway.
link
NKCSS 3534 days ago
It's limited to 10GB; so even if you wanted to, it won't :)
link
windowsworkstoo 3534 days ago
Trivial to sub the express edition for developer edition and you are away
link
NKCSS 3533 days ago
You know that's not allowed, right? Dev can only be used locally on your own machine, never to run anything other people can access.
link
windowsworkstoo 3533 days ago
Yes, why else would you be running SQL in a container for if not for dev....10GB is fuck all, and it's nice having multiple versions of a large test (or sanitized prod) backup available locally, which can easily be greater than 10GB
link
partisan 3533 days ago
"fuck all" - Absolutely nothing at all, the most extreme degree of nothing.
link
mattmanser 3534 days ago
You can only have a maximum 10 gb database on SQL Express, no point doing any of those things with that.
link
deviate_X 3533 days ago
I think 10gb is quite a lot of data for any database system, well at least it used to be!
link
mattmanser 3533 days ago
Even a one man band can easily afford a dedicated server to keep an entire 10Gb db in memory at all times.
link
fleitz 3534 days ago
The purpose of containers is that computers are now large enough that one computer can do the job of many previously smaller computers.

One your workload exceeds that of a normal run of the mill server containers are no longer a good idea. So basically once you start needing to do that which is mostly pointless now anyway with SSDs that would about the time when containers would also be ill suited to your workload.

Also, if you're running docker in prod, have fun :)

link
jdoliner 3534 days ago
If you schedule it on Kubernetes as a pet set you could give each container a consistent virtual disk from your cloud provider. Of course... your cloud provider also has SQL as a service, so that's probably a cheaper option.
link