Articles

Technical Article

Middle Tier Application Data Caching with SQL Server 2000

Middle tier applications often use a single database management system (DBMS) to store data, which can expose scaling limitations as the number of user requests increases. Caching, a technique used to increase application performance by copying data and then using the copied data in place of the original data, can dramatically increase the throughput (the number of application requests serviceable per unit time) and scalability of middle tier applications.

2002-03-08

2,221 reads

Technical Article

Performance Comparison: Data Access Techniques

Architectural choices for data access affect performance, scalability, maintainability, and usability. This article focuses on the performance aspects of these choices by comparing relative performance of various data access techniques, including Microsoft® ADO.NET Command, DataReader, DataSet, and XML Reader in common application scenarios with a Microsoft SQL Server™ 2000 database.

2002-03-01

2,857 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