Paul White (@SQL_Kiwi) kicks off a new blog series about ACID – atomic, consistent, isolated, durable – and how many people make incorrect assumptions about how these things work in SQL Server.
Aaron Bertrand (@AaronBertrand), of SQL Sentry, follows up his original running totals post with an article describing different ways to achieve the same types of results for more complex grouping and aggregation.
After a discussion with a colleague, SQL Sentry's Aaron Bertrand (@AaronBertrand) takes a look at the IDENT_CURRENT() function, and demonstrates how it cannot be relied upon for reporting the IDENTITY value that was generated – even under the SERIALIZABLE isolation level.
SQL Sentry's Aaron Bertrand (@AaronBertrand) talks a little more about in-memory table-valued parameters, and explains why some scenarios you test may not demonstrate the power of this technology.
Benjamin Nevarez (@BenjaminNevarez) gives us some insight into the new cardinality estimator in SQL Server 2014 – both how it works as well as how to keep the functionality of the current version of the estimator.
SQL Sentry's Aaron Bertrand (@AaronBertrand) investigates a new possibility in SQL Server 2014: creating and using memory-optimized table-valued parameters.
SQL Sentry's Aaron Bertrand (@AaronBertrand) investigates a deadlock issue with alias types and table-valued parameters, and the Connect items that have sprung up about this issue.
