Additional Articles


External Article

Using Indexes to Bypass Locks

One of the issues you'll face with SQL Server is blocking which is caused by other processes that are holding locks on objects. Until the locks are removed on an object the next process will wait before proceeding. This is a common process that runs within SQL Server to ensure data integrity, but depending on how transactions are run this can cause some issues. Are there ways to get around blocking by using different indexes to cover the queries that may be running?

2008-05-02

3,383 reads

External Article

SQL Server 2005 Express Edition - Part 21 - Using Replication Management Objects

Recent installments of this series have demonstrated SQL Server 2005 Express Edition's replication characteristics by taking advantage of replication-specific executables and T-SQL code combined with Windows Synchronization Manager and Web Synchronization technologies. This article explores another method of reaching the same goal, which involves Replication Management Objects (RMO).

2008-04-30

2,233 reads

Blogs

Don’t Miss Out – SQL Server 2025 Unleashed Training Starts Next Monday!

By

Next Monday, March 9, 2026, my one-day live online training SQL Server 2025 Unleashed:...

What is ALM in Fabric?

By

As someone who’s worked with data for over 20 years and with many cloud...

The Most Successful Startups in 2025 — And What They Have in Common

By

2025 belongs to the AI startups. If you peek into the tech headlines, you’ll...

Read the latest Blogs

Forums

A Quick Restore

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Quick Restore

Guarding Against SQL Injection at the Database Layer (SQL Server)

By tedo

Comments posted to this topic are about the item Guarding Against SQL Injection at...

Ola Hallengren Index Optimize Maintenance can we have data compression = page

By JSB_89

I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...

Visit the forum

Question of the Day

A Quick Restore

While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:

USE DNRTest

BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak'
GO
/*
Bunch of stuff tested here
*/RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACE
What happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance.

See possible answers