Part 1: How to solve the transactional issues of isolation levels
Transaction Isolation levels are described in terms of which concurrency side-effects, such as dirty reads or phantom reads, are allowed.
2013-05-01
10,197 reads
Transaction Isolation levels are described in terms of which concurrency side-effects, such as dirty reads or phantom reads, are allowed.
2013-05-01
10,197 reads
2012-11-21
2,116 reads
2012-04-19
2,019 reads
2010-07-06
3,100 reads
2009-03-19
4,057 reads
2009-03-05
3,689 reads
Table locking hints provide developers much tighter control of their transactions. Look at the benefits and disadvantages of using the NOLOCK and READPAST table hints in SQL Server
2008-07-15
5,492 reads
When I put together the invitation for T-SQL Tuesday #202, I wasn't sure what...
By Steve Jones
My life has some crazy travel stretches for sure. Between speaking, office visits, customer...
In Part 1, we saw how ‘Vamana’ represents vectors as nodes, connects them with...
Comments posted to this topic are about the item Server-Level Table sizes
Comments posted to this topic are about the item Optional Parameter Plan Optimization in...
There is a table tmp_tab:
CREATE TABLE tmp_tab ( id int, val int );
INSERT INTO tmp_tab VALUES (1, 1), (2, NULL), (3, 3), (4, 4), (5, 5);You want to order the rows ids by the following expression:
ISNULL(val, id) + 1Which of the following queries produces the expected ordering and why? (Select all correct) See possible answers