3 Solutions For Auditing Long SQL Server Extracts or Loads
In this post, Tim Smith looks at the different options you can use to audit your SQL Server extracts and loads during the ETL process.
A General Way to Maintain History Tables
You will see here a way to handle history tables. This way only takes into account Date-based data cleanup but is easily generalizable.
Backup Preparations
This week Steve asks you to make sure you practice your restore skills periodically.
A Database Design Test
Steve Jones saw a database design test for developers, but he's never been given one.
Export data from SQL Server to Excel
What native SQL Server options are available to export to Excel? Jeremy Kadlec explains.
Handling Data Corruption
This week Steve Jones wonders what you might do if you discovered data corruption.
Scoring Outliers in Non-Normal Data with R
Using R to detect outliers is relatively easy, but most methods assume your data is normally distributed. How do you handle skewed datasets?
Azure Automation Methods
Tim Radney of SQLskills walks through multiple automation methods you can use to manage and maintain your Azure SQL Databases.
Blogs
Tooling for Success: The Best FinOps Tools and Technologies
By HeyMo0sh
As a DevOps person, I know that to make FinOps successful, you need more...
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...
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