Performance Myths: Table variables are always in-memory
Guest author Derik Hammer dismisses the common myth that table variables perform better than temp tables because they are always in memory.
Guest author Derik Hammer dismisses the common myth that table variables perform better than temp tables because they are always in memory.
In this article (consist from 2 parts) , I will be focusing on one of the practical solutions for management of internal SQL Server jobs in AlwaysOn Availability Groups scenarios.
SQL Data Mask is the latest prototype to come out of Redgate Foundry. It copies your database while anonymizing personal data, and you can use it to mask your databases right now, free of charge. Here are the details.
Steve Jones is off to Seattle for the rest of the week attending Microsoft Build 2017.
This article describes a lightweight copy-and-generate approach for making a sanitized version of a production database available to development teams with SQL Clone and SQL Data Generator.
When there are several SSIS projects with packages in a SQL Server Database or Data Warehouse development, automated deployments as part of Continuous Integration can get tricky. Nat Sundar describes how he created a Deployment script that is intended to provision a Data Warehouse for System Integrated testing (SIT).
In this chapter, we will show how to create a Machine Learning experiment from our Azure SQL Warehouse.
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...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
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