[1] https://blogs.technet.microsoft.com/dataplatforminsider/2016...
This is pretty neat. Wonder if people could use it to run other Windows stuff on Linux
Edit: formatting
https://www.microsoft.com/en-us/research/project/drawbridge/
I wonder if there's any chance they'd allow this mechanism to be used by 3rd parties to port their Windows services to run on non-Windows platforms. I doubt it...
The secondary benefit is removing the Windows OS licensing cost.
No offence, was just wondering why would anybody use it...
A fully integrated data platform suite with several tools that are best in class. SQL Server is not just a relational database engine, though that is at the core of most tools and services.
SQL Server is a SKU that includes many things:
* Relational engine
* In-memory OLTP (SQL compiles to native code)
* Columnstore indices for OLAP workloads
* The two above can be combined for real time analytics
* Embedded R engine in DB
* SSIS - data processing orchestration tool AND ETL tool
* SSRS - traditional reporting platform (with native mobile reports)
* SSAS - best in class OLAP engine/semantic layer
* MDS - Master Data Services (basically a rules engine)
* DQS - Data Quality Services (pluggable back end for data quality needs - batch or real time)
I'm personally a fully competent Linux sysadmin, and an extremely incompetent Windows sysadmin.
SQL Server is great, I love .NET, and the only thing holding me back all these years has been the Windows system requirement.
The only thing I see MSSQL on Linux being useful for is for development and testing purposes before deployment to a local server farm or the Azure cloud. (Even then, why not just run it on your Windows dev machine?) Honest question: What's the scenario where you'd license a system to run on Linux in production? To me, this is interesting, from the virtualization standpoint, but it seems like a solution in search of a problem.
To answer your question directly...
Don't think of it from the perspective of "green field" development where you're building something from scratch.
While "green field" development is every dev's dream, the overwhelming majority of dev work involves maintaining and integrating with existing services. There are lots of MSSQL installations out there, after all.
On another note, I know soooo many developers for whom "SQL" is synonymous with "MySQL." MySQL is okay, but they should know that Postgres and MSSQL offer a lot of programmer-friendly things that make working with them a heck of a lot more fun than MySQL. Different index types, data types, window functions, CTEs, etc.
But it's like SQL Server on Windows Server Nano - nobody asks for it, because only full system has required tools and features.
It is not very difficult to create linux packages, writing microsoft has figured it out makes it sound as if its rocket science. It also sounds as if these packages are for 'linux' but the ones mentioned in the article are specifically for CentOS linux.
And as far as i understand they only released packages for CentOS/REHL and Ubuntu. Not all linux distributions.
sudo curl ... > /path/to/local/file
The simpler approach is:
curl https://horrid.site.sh/ | sudo tee /etc/blah/pathOn Linux there are Oracle, DB2, Postgres, MySQL, ... and in near future MSSQL too. Depending on the use case, choose wisely. There are many nice features in all of these databases, and several little documented dark edges that you better know about.
As for its performance and features, I have run PostgreSQL, MySQL, and SQL Server in production on large workloads and am a big fan of PostgreSQL. That said, I've encountered the fewest sharp edges and disappointments with SQL Server. It is a very respectable RDBMS and it's great that it's now available on Linux.
But to be fair it was an example of the wrong tool used badly in the wrong situation deployed in a poor environment.
And yes, it's good to have a choice. Some software is designed to run in combination with MSSQL. So it's good that they ported it to Linux.