External Article

In-Memory OLTP: Row Visibility in SQL Server’s MVCC

SQL Server's In-memory OLTP is fast, due to its multi-valued concurrency control (MVCC). MVCC avoids the need for locks by arranging for each user connected to the database to see a snapshot of the rows of the tables at a point in time, No changes made by the user will be seen by other users of the database until the changes have been completed and committed. It is conceptually simple but does the user always see the correct version of a row under all circumstances? Shel Burkow explains.

External Article

DELETE Operation in SQL Server HEAPs

You should stick to using tables in SQL Server, rather than heaps that have no clustered index, unless you have well-considered reasons to choose heaps. However, there are uses for heaps in special circumstances, and it is useful to know what these uses are, and when you should avoid heaps. Uwe Ricken explains, and demonstrates why you'd be unwise to use heaps rather than tables when the data is liable to change.

Blogs

The DIY Cost of Masking Test Data For Smaller Organizations

By

One of the things I’ve tried hard to do in database development situations if...

T-SQL Tuesday #196 – Two risky career decisions I made

By

The T-SQL Tuesday topic this month comes James Serra. What career risks have you...

T-SQL Tuesday #192: What career risks have you taken?

By

This T-SQL Tuesday is hosted by the one and only James Serra – literally...

Read the latest Blogs

Forums

XACT_ABORT being set to ON by web services

By zoggling

We have two "identical" instances of an ASP.NET web service (or so I have...

OPENQUERY Flexibility

By Steve Jones - SSC Editor

Comments posted to this topic are about the item OPENQUERY Flexibility

A Full Shutdown

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Full Shutdown

Visit the forum

Question of the Day

OPENQUERY Flexibility

Which of these are valid OPENQUERY() uses?

See possible answers