As you embark on your own Database DevOps journey you are going to hear many new concepts and phrases, but what do they mean and why are they important to consider? Join Grant Fritchey live as he breaks down the key concepts and terminologies around Database DevOps.
2022-10-24
Learn how and why to use THROW in your SQL Server code to be able to better handle errors that may occur during code execution.
2022-10-24
This article tracks down a problem with Availability Groups due to network bandwidth.
2022-10-21 (first published: 2022-08-09)
5,224 reads
There's still time to register for Summit and unlock access to over 300 sessions. Join peers and industry leaders in the data community homecoming. Get $200 off on the 3-Day Conference pass (in-person) with code REDGATEVIP or 50% off on the 3-Day online pass with code RGVIPONLINE
2022-10-21
2022-10-21
Learn how you can easily analyze the data lineage in your SQL Server database.
2022-10-19
9,941 reads
Take on the challenge of deploying database changes every 30 minutes in Redgate's Summit pre-con 'The Journey from Manual Deployments to Database DevOps' on November 15.
Hosted by Steve Jones, Grant Fritchey and Redgate DevOps experts, you'll start with a manual process and slowly implement changes that allow you to reap the benefits of automation.
2022-10-19
Before data can be read from of a SQL Server database table, the table needs to contain rows of data. One of the most typical ways to get data into a table is to use the INSERT statement. One row or multiple rows can be inserted with a single execution of an INSERT statement. You can even use the output of a stored procedure to insert rows. In this article, I will explore the basics of inserting data into a SQL Server table using the INSERT statement.
2022-10-19
Motivation At some point in the carrer, we have come across the problem of hard-coded values in SELECT or WHERE clauses. And we all agree that these hardcoded values must be parametrised. This bad habit usually backfires when we need to troubleshoot a query. These hardcoded values are usually a business role baked in the […]
2022-10-18 (first published: 2022-09-02)
11,342 reads
Learn the basics of using Terraform to declaratively specify how to configure resources in infrastructure.
2022-10-17 (first published: 2022-08-26)
14,616 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers