Monday Monitor Tips: Looking Back in Time
Often we find out about a problem reported by a customer after the incident has passed. This might be from a trouble ticket or even an email that we...
2025-03-24
149 reads
Often we find out about a problem reported by a customer after the incident has passed. This might be from a trouble ticket or even an email that we...
2025-03-24
149 reads
In today’s data-driven world, organizations need the ability to analyze and act on data as it flows in real time. Microsoft Fabric provides a powerful ecosystem for real-time intelligence,...
2025-03-24 (first published: 2025-03-12)
7,352 reads
Low-code solutions often accelerate development and make tasks accessible to people who can’t or don’t want to write their own code. But it’s important to remember that it’s a...
2025-03-24
17 reads
Low-code solutions often accelerate development and make tasks accessible to people who can’t or don’t want to write their own code. But it’s important to remember that it’s a...
2025-03-24
10 reads
Low-code solutions often accelerate development and make tasks accessible to people who can’t or don’t want to write their own code. But it’s important to remember that it’s a...
2025-03-24
29 reads
Thank you to Deborah Melkin for hosting TSQL Tuesday this month! I’ve always considered mentoring and sponsorship very structured. Now, I wonder if they’re also small things we do...
2025-03-24 (first published: 2025-03-11)
6,591 reads
The main thing is to keep the main thing the main thing. – from Excellent Advice for Living We can summarize this advice as focus on what’s important. I...
2025-03-21
11 reads
We published an article recently at SQL Server Central on Tally Tables in Fabric from John Miner. In it he showed how this can be efficient. A day after...
2025-03-21 (first published: 2025-03-12)
6,963 reads
This month’s T-SQL Tuesday blog party is hosted by Deborah Melkin – Data Platform MVP, WIT co-lead and WITspiration founder. Deb’s invitation is to blog about mentoring and sponsorship. What...
2025-03-21 (first published: 2025-03-11)
6,659 reads
When Covid took out the PASS organization, I had someone say to me, “Well, that’s the end of the data community.” My response was pretty simple, “Nope. The community...
2025-03-20
17 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