Contest

Technical Article

The SQL Server BI Quiz

  • Article

From MVP Jacob Sebastian, creator of the T-SQL Challenges, there is a BI quiz throughout the month of June. Enter and answer questions each day for the chance to win prizes.

2011-06-02

2,796 reads

Technical Article

T-SQL Quiz 2011

  • Article

The 2011 edition of MVP Jacob Sebastian's T-SQL Quiz is underway. You can take part in the quiz each day, submitting your answers for the chance to show off your knowledge and perhaps win some prizes.

2011-03-04

4,394 reads

Technical Article

The SQL Server Quiz

  • Article

There's a SQL Server quiz taking place during the next 31 days, challenging you to answer questions from a number of SQL Server experts and MVPs.

2010-10-01

2,954 reads

Blogs

Trace Flag 1448 – Lessons from a Technical Interview

By

In SQL Server environments where transactional replication runs alongside Always On Availability Groups (AGs),...

Disable the sa login in SQL Server (and sleep better)

By

Disable the sa login in SQL Server (and sleep better)If you run SQL Server...

Leadership in Times of Change: Guiding Teams Through Uncertainty, Disruption, and Transformation

By

Change is inevitable. What separates thriving organizations from those that falter is not the...

Read the latest Blogs

Forums

Create an HTML Report on the Status of SQL Server Agent Jobs

By Nisarg Upadhyay

Comments posted to this topic are about the item Create an HTML Report on...

Be Wary of Data

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Be Wary of Data

Locking Hierarchies

By Uwe Ricken

Comments posted to this topic are about the item Locking Hierarchies

Visit the forum

Question of the Day

Locking Hierarchies

You have a table [dbo].[orders] without a Clustered Index (Heap). The table does not have any other nonclustered indexes! You rund the following command in Read Committed Isolation Level:

SELECTo_orderdate,
        o_orderkey,
        o_custkey,
        o_storekey
FROMdbo.orders
WHEREo_orderkey = 3877;

What locking hierarchy will Microsoft SQL Server use?

 

See possible answers