Additional Articles


External Article

A Hybrid Approach to Database DevOps

A flexible approach to Database DevOps where the team maintain the current state of the database in version control, during development, and then at key stages generate and test the migrations script that will deploy the changes to the target database, safely.

2020-05-14

External Article

How to ACTUALLY save money in the cloud with SQL Server

We have all heard migrating to the cloud can save you money and there are several ways moving your SQL Server workloads to the cloud can save your organization money. But, there are also missteps that can eat away at the savings, performance and even your availability creating instead an expensive, ineffective, difficult to manage cloud infrastructure.

2020-05-14

External Article

Introduction to Azure SQL Database Instance Pools

In one of the article, Considerations for Deploying Azure SQL Database Managed Instances, recently published on this site, basic characteristics of Azure SQL Database Managed Instance were described. Its biggest selling points include nearly full compatibility with on-premises SQL Server deployments, support for SQL Server Agent, and additional security associated with its Azure virtual network integration.

2020-05-13

Technical Article

Using SQL Clone and SQL Change Automation to switch database branches

Learn how to use SQL Clone together with Git hooks and SQL Change Automation to branch your database in Git as easily as your code. By enabling multiple copies of the same database to exist on a single instance, the integration of these tools allows seamless database branch switching.

You rated this post out of 5. Change rating

2020-05-12

External Article

How to Attach a SQL Server Database without a Transaction Log and with Open Transactions

You want to attach a SQL Server database that does not have the transaction log files and get the following error: "The log cannot be rebuilt because there were open transactions/users when the database was shutdown, no checkpoint occurred to the database, or the database was read-only. This error could occur if the transaction log file was manually deleted or lost due to a hardware or environment failure." In this tip I will help you to successfully attach the transaction log to the problematic SQL Server database.

2020-05-07

Blogs

TempDB Internals – What’s New (SQL Server 2016 to 2022)

By

I wrote about TempDB Internals and understand that Tempdb plays very important role on...

Blog a Day – Day 2: Generative AI, Multimodal Systems, and Agent AI

By

continuing from Day 1 where we covered the history of AI and GPT family,...

A Wellbeing Day at Redgate

By

It’s a day off for Redgate today. This is our annual wellbeing day, where...

Read the latest Blogs

Forums

adage acting funny

By stan

Hi, i know this is a shot in the dark.  i dont know what...

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 Terry Jago

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

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