[allegory]

Just a note from me, as I tried one for a week.

Not enough RAM!

My 2011 MBP has 16Gb of RAM and my 2014 HP Z420 has 32Gb of RAM.

I can barely spin up our product on a machine with 8Gb of RAM without killing everything else I'm doing on first. Then SQL Server doesn't give the RAM back inevitably leading to the service being restarted to release it. Granted this is a big product but in this day and age, 8Gb shouldn't be the cap for anything.

Also both the keyboards were shitty and the thing crashed occasionally (blue screen) when I tried plugging it into my desktop monitor - an old 22" Dell TFT.

The big thing for me, is that I actually had a better experience using my Android tablet with a keyboard/mouse plugged in and remote desktop to my workstation in the office. That kills the massively powerful portable computer use case dead for me. Was perfectly usable over a 3G connection as well.

[GFischer]

I wonder what the heck are you developing :) .

Maybe a solution would be to have SQL Server on a virtual machine, or use an Azure SQL instance (in my very limited trial latency was a bit annoying though).

[allegory]

15 years of legacy crap :)

I need a full data volume available as a lot of the stuff requires heavy performance testing.