@McNets yup, I noticed that too: I don't know exactly why 2016 is slower. My guess is that it is the database creation step — maybe that's been streamlined in vNext, or maybe it's faster on Linux — I'll find out when I add a Windows vNext VM.
That is a myth. They compile down to the same CLR. However the compiler for the same routine may come out slightly differently in the CLR. So for certain routines some may be slightly better like (0.0000001%) faster in C# and vice versa for VB.NET, but they are both running off the same common...
"People who like Postgres and MySQL tend to vote down answers that mention SQL Server and Oracle, people who like Waterfall tend to down vote answers that mention Agile and so forth.": Utter nonsense. I may like Postgres and SQL Server, and dislike MySQL but I never base my voting on my likes for a product. There is zero evidence that users vote the way you claim. — ypercubeᵀᴹ11 hours ago
@JackDouglas You could indeed do that. But before you do, can you confirm that the newly created databases are all created with AUTO_CLOSE set ON? I believe that is the default for Express, and may explain the slowness. Consider ALTER DATABASE xxx SET AUTO_CLOSE OFF; immediately after/as part of creating the database.
Depending on how slow the db close/reopen process is on your setup that might be it. Databases unused for a while could be set back to AUTO_CLOSE=ON to conserve resources if that makes sense for you.