A New Word: Heartspur
heartspur – n. an unexpected surge of emotion in response to a seemingly innocuous trigger – the distinctive squeal of a rusty fence, a key change in an old...
2023-11-10
20 reads
heartspur – n. an unexpected surge of emotion in response to a seemingly innocuous trigger – the distinctive squeal of a rusty fence, a key change in an old...
2023-11-10
20 reads
There was an update to Flyway Desktop which lets you see the type of database your project is associated with, and this post shows how to get this in...
2023-11-10
92 reads
Games Night is back at the Summit, this time on Wednesday night in a large space for 200 people plus to enjoy some fun with friends and colleagues. This...
2023-11-10 (first published: 2023-11-02)
168 reads
2023-11-10
515 reads
The 2023 First-Timer guide to the PASS Data Community Summit is available from Edwin Sarmiento
2023-11-10
618 reads
Edwin Sarmiento has a great First Timer Guide for the PASS Data Community Summit, which is updated for 2023. He’s been compiling this since 2016, and it’s worth reading....
2023-11-09
75 reads
Learn how to use the notebook feature of Azure Data Studio to keep a set of queries together with some documentation.
2023-11-09 (first published: 2019-04-11)
20,374 reads
2023-11-08
449 reads
In the past, Steve hasn't often felt management considered databases to be important, but that is changing.
2023-11-08
173 reads
Learn the basics of how Dynamic Data Masking can be used to obfuscate data in SQL Server 2016+.
2023-11-08 (first published: 2016-03-15)
8,392 reads
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