Indirect checkpoint is the recommended configuration, especially on systems with large memory footprints and default for databases created in SQL Server 2016.
Sherlee Dizon looks at the basic differences between char, nchar, varchar, and nvarchar, as well as what to be aware of when using each data type.
Dynamic Data Masking is an exciting new feature in SQL Server 2016, allowing DBAs to centrally set a mask that is returned for a table column instead of the actual data, limiting what information is returned to certain users in a consistent and reliable way. What’s more, Redgate SQL Compare safely and reliably handles your DDM changes. Data Platform MVP Steve Jones explains more.
A guide to using Visual Studio to create U-SQL projects and scripts.
The march to the cloud is ongoing and Steve Jones says you should prepare yourself. Even if your company doesn't move.
Rob Farley looks at information exposed in query plans about residual predicates and actual rows read, showing how Plan Explorer helps identify the issue.
Toady we are going to make a copy and export your DB to Azure Storage. Lets get started.
Today Steve Jones talks about the problem of having code that people are afraid to change or deploy.
Although it is well-known that the best efforts of a development team can be derailed by mistakes in the architecture, design and general governance of a development project, few attempts have been made to describe what needs to be done to increase the chances of success in the development of a database application. William Brewer steps into the breach to itemise what a delivery team needs to succeed.
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