This technical session shows how to configure the new SQL Server 2017 release on the Linux platform for production-ready architecture, including topics such as setting up additional drives and backing up over the network.
Software developers – native SQL Server development on non-Windows-based development workstations & laptops
LAMP stack injection
Small biz – low cost with no Windows-layer operating expenses
New business – low cost with
Starting in SQL Server 2005, drawbridge allowed Microsoft to avoid most of the dependency on windows by embedding their own mini operating system inside of SQL Server. The Windows layer adds all sort of potential functionality, but they wanted SQL Server to handle it so they would have the most control over it possible.
For example, SQL Server uses unbuffered I/O to bypass the Windows caching layer completely, and implements its own caching layer – that we know as the buffer pool. It also does its own context switching instead of letting the OS manage this.
So, it does not rely on Windows itself nearly as much as previously thought.
The final snapshot of the code from Drawbridge was merged with SQLOS to create something called SQLPAL, the SQL Platform Abstraction Layer. It created a slimmed down version of Win32 with performance engineered for maximum SQL Server performance.
IT’s the same code!
https://arstechnica.com/information-technology/2016/12/how-an-old-drawbridge-helped-microsoft-bring-sql-server-to-linux/
/var is for messages and files that change constantly as a result of user programs