SQL Clone

External Article

Using striped backups with SQL Clone

  • Article

If you’re a Redgate SQL Backup customer, occasionally you’ll need to convert your SQL Backup (.sqb) files to the native SQL Server backup format (.bak), perhaps to perform native database restores on a server where SQL Backup isn’t installed. This produces a striped backup, because each thread used when making the backup will produce a separate file. Can we use a striped backup produced in this way, or indeed any striped backup, as the source for a SQL Clone image? Short answer: we can! Let’s see how that works.

2017-05-29

2,237 reads

External Article

Why is my clone so small?

  • Article

Using very few megabytes and taking very little time, SQL Clone can quickly creates multiple copies of very large databases. How? It might sound like magic, but it's not; in this blog post Redgate developer Chris Hurley goes into the details of how the technology works.

2017-05-03

3,687 reads

Blogs

Why Developers Shouldn’t Have sysadmin access in SQL Server

By

 Why Developers Shouldn’t Have sysadmin access in SQL Server 7 reasons—and exactly what to do instead It...

A New Word: Ecstatic Shock

By

ecstatic shock – n. a surge of energy upon catching a glimpse from someone...

The CDO’s Playbook for AI Driven Decision Making

By

The New Arena of Leadership The role of the Chief Data Officer is no...

Read the latest Blogs

Forums

The Foundation of a Successful Doctoral Journey

By Ariel Wilson

Writing a PhD proposal is one of the most crucial steps in academic research....

sp_prepare and sp_execute vs sp_executesql

By rajemessage 14195

I have noticed sp_executesql also makes a single plan for a stmt with parameter...

Who am I?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Who am I?

Visit the forum

Question of the Day

Who am I?

If I want to track which login called a stored procedure and use the value in an audit, what function can I use to replace the xxx below? 

create procedure AddNewCustomer
  @customername varchar(200)
AS
BEGIN
    DECLARE @added VARCHAR(100)
    SELECT @added = xxx

    IF @customername IS NOT NULL
      INSERT dbo.Customer
      (
          CustomerName,
          AddedBy 
      )
      VALUES
      (@customername, @added)
END

See possible answers