Articles

SQLServerCentral Article

DIY Database Clones

This article explores the 'shadow copy' and 'disk virtualization' services built into the Windows operating system and explains a basic solution demonstrating how the technology is used to copy the data and log files for a live SQL Server database into an 'image', from which we can create multiple, lightweight copies, or clones, of the original database.

5 (6)

You rated this post out of 5. Change rating

2025-10-22 (first published: )

5,963 reads

External Article

T‑SQL BULK INSERT vs OPENROWSET: CSV Imports, File Access Gotchas, and A PowerShell Script

Most SQL bulk insert and SQL Server openrowset tutorials skip file access issues that can stop imports cold. Both the bulk insert statement and openrowset function rely on the SQL Server service account to read a source file. The SQL Server service account must have read permission on the file or its folder. It is also convenient to have read & execute as well as list folder content permissions.

2025-10-17

Blogs

Creating a Striped Backup Set with AI

By

I needed to test a striped backup, so I decided to ask the AI’s...

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...

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...

Automatically generate tabular model partitions

By richard.powell 56882

Hi. I hope someone can give some useful suggestions. My workplace have a suite...

SQLPS and syspolicy_purge_history job

By schleep

The SQLPS.exe file has gone AWOL on 2 of my 4 SQL servers, ie,...

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