SQL Relay

Technical Article

Registration is open for SQL Relay

  • Article

SQL Relay is an annual community-run series of SQL Server training events across the UK. SQL Relay will run 8, 1-day conferences over the course of 2 weeks starting June 17th. Speakers from Microsoft, global IT companies, and a host of MVPs, are covering topics on DBA, business intelligence, and development.

You rated this post out of 5. Change rating

2013-04-26

3,302 reads

Technical Article

SQL Relay 2012

  • Article

This May brings SQL Server experts to your locality; full day seminars in Edinburgh, Manchester, Birmingham, Bristol and London. Overview sessions from Microsoft in the morning, Deep Dive sessions in the afternoon from SQL Server MVP's and evening community events.

5 (1)

You rated this post out of 5. Change rating

2012-05-21 (first published: )

4,173 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