A blog for members of the SQL Server SQLOS team to share information and get your feedback.

New SQLOS features in SQL Server 2012

Here's a quick summary of SQLOS feature enhancements going into SQL Server 2012. Most of these are already in the CTP3 pre-release, except for the Resource Governor enhancements which will be in the release candidate. We've blogged about a couple of these items before. I plan to add detail. Let me know which ones you'd like to see more on:

Comment Notification

Comments

Thanks for the update, but it seems so antiquated having this Windows O/S & SQL O/S model where the DBMS O/S implements a complex model of putting threads to sleep merely to work around the vagarities of the host's pre-emptive task scheduling model, not to mention the accompanying memory management problems that are inherently associated with task scheduling.

Why not build an integrated Windows SQL edition which does task scheduling & resource management specifically the way the DBMS needs it?

The current model stems from the original Sybase partnership, consequent split where Microsoft wanted to show off Windows pre-emptive multi-tasking (4x, 6x) but back-flipped in 1998 with the UMS in SQL7. The problem with UMS / SQLOS in the DBMS is that it only makes sense where you're targeting multiple platforms, which SQL Server has never done (perhaps other than OS2 / Windows in the early days).

So, today we live with an illogical architecture (Windows OS + SQL OS) which has all sorts of spin off complexities & problems.

may be they are putting so much effort in SQLOS because they are planning to build SQLSERVER a cross platform product :)?

But clearly if you start reading documents on SQLOS , memory node, cpu node etc, you end up getting confused who is doing what. Is it SQLOS who is charge of everything allocating all kind of memory by itself or windows memory managers doing all kind of work on behalf of SQLOS or both are doing work in bits and pieces , some one allocating buffer pool and others user cache etc .

They need to work on proper documentations also explaining clear boundaries of different memory managers .