Articles

External Article

Work Around Errors in Database Web Apps

ne of the issues you face when building Web applications is handling the errors you encounter when interacting with a back-end database. I was recently working with someone to create a new Web site with SQL Server™, ActiveX® Data Objects (ADO), and ASP. Lots of little things came up that I thought were worth sharing with MIND readers, so I'll focus this column on what I learned from this experience and the solutions to many of the problems I faced.

2001-07-13

1,579 reads

Technical Article

Quarter of a Century Competition on P2P

P2P, the programmer's resource centre from Wrox Press, reached a milestone of 25,000 subscribers this week. To celebrate this fact, Wrox are giving away $1000 worth of books and ASPToday subscriptions in a free prize draw. For more details on how to enter, please visit: http://p2p.wrox.com/25k.asp. The draw will be made on July 16th.

2001-07-12

45 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