We might be smart in one area, but not others. That's worth remembering.
First off, I understand if you read the headline and you have a knee-jerk reaction. I totally understand that there are a lot of people out there who hate AI, and believe me, I hate most uses of it. Lots of its advice can be misleading at best, and absolute garbage at worst.
Microsoft gives a year in review from the SQL Server and Azure SQL teams. Steve sees a lot of accomplishments from this past year.
I have been working in various computer languages for a long time. When I saw that the || operator was coming, I was a bit confused as to why we needed this, and how it would work. After all, this is a part of other languages. I decided to dig in a bit. This is […]
Today Steve asks what value you get from attending conferences or other events.
SQL Server 2025 includes new features and enhancements. In the previous SQL Server 2025 tips, we have explored many new features. Have you explored the new Product() function? If not, this will walk you through the Product() function with several examples.
Learn how backup and restore work in Azure SQL Hyperscale in this next level in the stairway series.
Steve sees a lot of challenges ahead for AI, especially in the area of labor and employment.
Securing SQL Server isn’t complicated, but it does require consistent attention to the areas where real risks arise, such as privileges, configuration, encryption, patching, and monitoring. This article outlines 15 practical, high-impact steps you can take to harden your SQL Server environment.
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