Have you ever longed for a way of making the delivery of databases more visible, predictable and measurable? Do you ever wish that they would be of better quality, quicker to change, and cost less? Grant Fritchey explains some of the secrets of doing Continuous Integration for Databases to relieve some of the pain-points of the Database Delivery process.
The following article will show how to extract terms occurrence from a SQL table.
Greg Larsen explores the different ways that you can encrypt your existing confidential data using Always Encrypted Columns in SQL Server 2016.
This article gives an overview of the Microsoft Azure SQL Data Warehouse architecture. The new platform-as-a service (PaaS) offering provides independent compute and storage scaling on demand and is currently in public preview.
An explanation as to what Log Shipping is and why it's still a viable solution in 2016.
The whole point of using a cloud service is to be able to use it intensively for a brief period just when it is needed and then clear out all your work when you've finished. This means automation to make the process as quick and easy as possible. It is likely to mean creating a VM, provisioning it from scratch and spinning it up using PowerShell. Relax, grab the popcorn, and let Adam Bertram show you how he does it in Azure.
Passwords are always a challenge, but are bad passwords the users' fault? Steve Jones has a few thoughts.
Arshad Ali demonstrates what the APPLY operator is, how it differs from regular JOINs, and what its applications are.
By HeyMo0sh
In my experience, FinOps success has never been just about tools or dashboards. It...
By HeyMo0sh
As a DevOps person, I know that to make FinOps successful, you need more...
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
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