Replace Bad Characters in Table
Learn how to clean bad characters from lots of data in this article.
Generating HTML from SQL Server Queries
You can produce HTML from SQL because SQL Server has built-in support for outputting XML, and HTML is best understood as a slightly odd dialect of XML that imparts meaning to predefined tags. There are plenty of edge cases where an HTML structure is the most obvious way of communicating tables, lists and directories. Where data is hierarchical, it can make even more sense. William Brewer gives a simple introduction to a few HTML-output techniques.
Classifying Sensitive Data
The ability to protect, and perhaps handle, sensitive data separately from other data is becoming more important. Steve Jones discusses the process and asks if it's something you perform on a regular basis.
Filegroup Restoring and Database Consistency
In this article, we'll explore a less used feature of SQL Server: filegroup restoring, feature that has an interesting consequence because database can become inconsistent without any warning and standard checks don't reveal any issue.
How to Read the Transaction Log File
Have you ever wanted to be able to see the actual transactions that are contained in the transaction log file? Greg Larsen shows you how to browse the transaction log using an undocumented function.
Improving Replication
If you have ideas for how to improve replication, Steve Jones is asking for them.
The Forgotten Editorial
Phil Factor reflects on the occasional benefits of document loss, whether accidental or less so.
Workplace Encounters: Using Volume Mount Points in SQL FCIs
How we overcame the A to Z Windows Drive-Letter limitation using Volume Mount Points
A DLM Approach to Database Testing
Database Lifecycle Management aims to make the development and modification of databases more predictable. Bugs are the source of more unpredictability than anything else, purely because it is so difficult to guess how long it will take to fix them. Good testing at all stages may take some time and effort, but it greatly reduces likelihood of the wildcard factor of the bug that is first detected during the deployment process; or worse, that gets into the production release.
Blogs
From Planning to Practice: Setting Up Your FinOps Framework
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
“We love to debate minutiae”
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
Advice I Like: Knots
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Forums
Restoring On Top II
Comments posted to this topic are about the item Restoring On Top II
SQL Art 2: St Patrick’s Day in SSMS (Shamrock + Pint + Pixel Text)
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Breaking Down Your Work
Comments posted to this topic are about the item Breaking Down Your Work
Question of the Day
Restoring On Top II
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