My home desktop (Intel Pentium G645) doesn't support virtualization and I guess this means I can't run this.
That CPU of course supports virtualization.
How Microsoft brought SQL Server to Linux
81–90 of 207 posts
Re: How Microsoft brought SQL Server to Linux
#82Earlier quoted context omitted.
Too bad that Windows 10 barely usable on itself. Every application looks different (yes they used to blame Linux/X11 on that one). It has two control panels (or three maybe), two web browsers shipped with it. Takes more than a minute to boot on a new and pretty formidable laptop. This is the fresh factory install. Can freeze the desktop while apparently doing something under the hood (installing updates? scanning mal…
> Too bad that Windows 10 barely usable on itself. I am always surprised to hear these statements. Hundreds of millions of people use W10, so it must be usable to some extent. I think it's also quite rare that the system stops for 5 minutes -- actually I've never seen that happening.
>I am always surprised to hear these statements.
No kidding. I use it every day nearly all day and I can count the number of times I've had the OS itself get in my way on 1 hand.
Re: How Microsoft brought SQL Server to Linux
#83Microsoft is playing a fantastic Linux game with putting Linux userspace on the Windows desktop where drivers and UI are far better than the Linux drivers and UI and putting SQL Server on Linux server where the Linux kernel is much stronger. They know their strengths and weaknesses and not afraid to play to them. Here's my writeup on setting up Windows 10 as a long, long time Linux user https://github.com/chx/chx.git…
Too bad that Windows 10 barely usable on itself. Every application looks different (yes they used to blame Linux/X11 on that one). It has two control panels (or three maybe), two web browsers shipped with it. Takes more than a minute to boot on a new and pretty formidable laptop. This is the fresh factory install. Can freeze the desktop while apparently doing something under the hood (installing updates? scanning mal…
Windows 10 is usable in every aspect.
Boot speed is pretty good and doesnt freeze like that.
Check your hardware if that is a fresh factory install. You are doing something wrong.
They are not common problems. They are yours.
Re: How Microsoft brought SQL Server to Linux
#84Earlier quoted context omitted.
A rewrite, or a "rewrite"? I've seen plenty of press articles about something MS "rewrote" from the ground up, including windows itself, and they are never true. Unless they actually started from a blank source repository then it was not a rewrite.
i was there, from 1995 on. It was a real rewrite. sybase's optimizer was the biggest piece of shit ever. losing predicates, functions that called each other multiple times to rewrite the tree. We didn't have docs on the page formats, we have to reverse engineer it. The only piece not completely rewritten in the first release in 7.0 shipping in 1998 was the tree/algebraizer that was the input to the query processor. i…
It would seem a lot of the protocol was kept though, no? IIRC there wasn't much diff between the mssql 6.5 protocol and mssql 7 protocol. I had been working with the freetds project in 1999/2000 and spent way too much time learning about some of that, although... it was 17 years ago and details are fading!
Re: How Microsoft brought SQL Server to Linux
#85Earlier quoted context omitted.
> Too bad that Windows 10 barely usable on itself. I am always surprised to hear these statements. Hundreds of millions of people use W10, so it must be usable to some extent. I think it's also quite rare that the system stops for 5 minutes -- actually I've never seen that happening.
Argumentum ad populum; people just don't know better. Also, I doubt it's really hundreds of millions (of people, as opposed to installs).
That was an anectodal evidence at first place.
Re: How Microsoft brought SQL Server to Linux
#86Earlier quoted context omitted.
SQL Server requires regular restarts? I find this hard to believe.
I don't know which version the parent looked at, but we had a mix of SQL Server 6.5 and 2000 servers. Those on 6.5 suffered from all kinds of phantom errors which a regular restart schedule fixed. SQL Server 2000 on the other hand was solid.
similar experience - worked with 6, 6.5 and 7 on NT 3.5 and NT 4. 4 was better, but it often was 4 itself which ended up needing rebooting, vs SQL Server itself, but... when one's on the other, does it make much of a difference? There wasn't an option to run MSSQL 7 on anything else, IIRC.
I do remember 7 on 4 was much improved re: requiring reboots, and the projects I was on ended up doing it periodically more out of proactive concern re: NT4 than real demonstrated problems with MSSQL 7. 1999 project had 80 NT servers running IIS reboot on a schedule every few hours with a big load balancer in front. 70+ up at any one time, always a handful being reboot and coming in and out of the pool. If we didn't proactively do it, they'd just go down anyway. IIRC that spoke more to IIS than NT but again... how can you necessarily tell the difference? Not rhetorical, there were probably good ways to dig in and try to determine root causes (and I think some folks tried or did) but it didn't mean we could actually do anything about it (like patch and recompile the NT kernel).
Re: How Microsoft brought SQL Server to Linux
#87Earlier quoted context omitted.
Hmm, I think HN needs a way to report either spam messages or users - this guy was created 6 mins ago, has two comments, both spam
Brainstorming with you: Maybe we could have another queue /possiblespam like we have for /newest? Or we could make a competition out of it: 1point for a correct spam identification -10 for false positive
This is way off topic, but that kind of simple gamification is "broken" because there are three Nash equilibrium, only one of which is actually marking spam correctly.
If everyone marks everything as spam, then anyone not also doing the same is "punished" because they are missing out on points they could get by marking more things as spam.
If everyone is marking everything as "not spam" then anyone marking spam as spam correctly is punished as having "false positives" because everyone else is marking it not spam.
To prevent those bad outcomes (which happen very quickly in some situations, I'll try to dig out real-world examples later) you need to know what is "really" spam and what isn't, but if you know that then you've already solved the problem you set out to solve with this system.
Re: How Microsoft brought SQL Server to Linux
#88Earlier quoted context omitted.
You get mostly working Kerberos. It's not quite that reliable.
What issues have you run into? I haven't encountered any problems. Admittedly I mostly use it for logging into servers with AD accounts (it will autocreate homedirs too!) and access controls via AD groups. You can permit SSH/sudo access through AD group memberships. SSH works with Kerberos SSO.
Mainly periodic random unexplainable KDC_ERR_C_PRINCIPAL_UNKNOWN which appears to be the Kerberos equivalent of "fuck you!"
Re: How Microsoft brought SQL Server to Linux
#89I would never recommend SQL Server on Linux for Enterprise production. - licensing costs are probably the same. If the cost of an additional Windows Server license is an argument, something else is going on. - recently having dealt with MS Enterprise support on Linux, it was an horrendous experience I can nobody recommend - an Enterprise with need for SQL Server without Windows Server support engineers? - did we see…
I think it's partly a hat-tip to ISVs using .NET. Entity Framework (Core and Desktop) works best with SQL Server, with whole .NET Core is cross-platform thing they let ISVs sell to Linux shops too. The alternative would be to mix EF with PostgreSQL or (horror of horrors) MySQL which is a pain-in-the-ass for testing/QA. ORMs are leaky abstractions!
If you're ponying up for a SQL Server license you can afford to pony up for the Windows license. But if you're not a Microsoft shop and you're buying .NET Core-based COTS you can skip the license fees and install SQL Server vNext Express on your Linux machines. (Up to the point where you max out Express and have to cough up for Standard anyway.)
Re: How Microsoft brought SQL Server to Linux
#90Microsoft is playing a fantastic Linux game with putting Linux userspace on the Windows desktop where drivers and UI are far better than the Linux drivers and UI and putting SQL Server on Linux server where the Linux kernel is much stronger. They know their strengths and weaknesses and not afraid to play to them. Here's my writeup on setting up Windows 10 as a long, long time Linux user https://github.com/chx/chx.git…
Thats if you dont mind the hugely privacy invasive win10 environment to begin with.
It is way less than what Google does on my Android devices.
Now Google Maps even asks me to upload pictures of places where I happen to be.