The Geek Costume
This Friday Steve Jones has another fun poll. A question on the geek costume that might excite you the most.
Does NoSQL = NoDBA?
There’s a joke doing the rounds at SQL conferences and seminars: three DBAs walk into a NoSQL bar and leave when they can’t find a table. You may have heard it before, but it made Matt Hilbert sit down and ponder. What’s happening? Is there a division opening up between the newly fashionable NoSQL followers and DBAs? Matt enters the world of NoSQL to investigate.
Automating Red Gate SQL Compare with MSSQL Server Agent
How to compare two databases and email the results to every one who needs to know
SQL Overview SSIS Package III - Full Package
Continuing on with his series on reporting for your SQL Server, David Bird brings together the series with the full package used for building the report.s
Stuck in a Rut
What do people do when their job doesn't require a lot of technical skills? Steve Jones has a few thoughts.
Data Mining Part 19: Excel and Data Mining, Samples, Queries
This lesson explains how to Clean Data, Explore Data, get Samples of Data, Classify and query a Data Mining Model.
Data Mining Part 19: Excel and Data Mining, Samples, Queries
This lesson explains how to Clean Data, Explore Data, get Samples of Data, Classify and query a Data Mining Model.
Triple Digits
Salaries for data professionals have risen quite a bit, according to the latest salary survey. That's good for those of us working with SQL Server.
Data Is Crazier than You Think
As a society, we have an unrealistic respect for data, especially if it has a decimal point somewhere and uses metric units. We who are in the business of data need to cultivate a renewed interest in the sceptical and rigorous science of statistics: it is too important to leave to 'Data Scientists'. If the data is wrong, or the way we analyse or report it is misleading, much of what we do is pointless.
SQL Monitor Custom Metric: Average I/O Stalls
This metric is a great general indicator of performance problems. High stall times indicate I/O problems, which can be attributed to busy physical disks or queries that return large data sets to the client.
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