The Face of BI for SQL Server
Donald Farmer recently left Microsoft, and he will be missed, but Steve Jones knows that there will be new faces to get to know.
Check that what you expected is actually what you got - DB's and SQLCMD
I feel that it is wise move for a script to actually check itself that the database connection that is...
ShowPlan Operator of the Week - Merge Join
Did you ever wonder how and why your indexes affect the performances of joins? Once you've read Fabiano Amorim's unforgettable explanation, you'll learn to love the MERGE operator, and plan your indexes so as to allow the Query Optimiser to use it.
XQuery for the Non-Expert – @Variable Use
Talk to the Experts
In a previous post, I discussed the exist() method as part of the XQuery for the Non-Expert...
Skunk Works
The idea of a skunk works is to build a project that works under the radar, by a small and loosely organized group of people. Used to fuel innovation, this is an idea that you might apply to SQL Server BI projects.
Multi-subnet Failover Clusters
Multi-subnet Failover Clusters
I want to take a closer look at one of the new features in SQL Server Denali. While...
SQL Server Unit Testing with tSQLt
When one considers the amount of time and effort that Unit Testing consumes for the Database Developer, is surprising how few good SQL Server Test frameworks are around. tSQLt , which is open source and free to use, is one of the frameworks that provide a simple way to populate a table with test data as part of the unit test, and check the results with what should be expected. Sebastian Meine and Dennis Lloyd, who created tSQLt, explain
Why Every DBA Needs a Buddy
If you truly desire to be an effective SQL Server Database Administrator then you absolutely must have a buddy.
SQL Server...
Data Scientists
Would you want to be a data scientist? Are you one now? Steve Jones talks about this skill that we might appreciate in our daily work.
Making a more reliable and flexible sp_MSforeachdb
While the system procedure sp_MSforeachdb is neither documented nor officially supported, most SQL Server professionals have used it at one time or another. This is typically for ad hoc maintenance tasks, but many people (myself included) have used this type of looping activity in permanent routines. Sadly, I have discovered instances where, under heavy load and/or with a large number of databases, the procedure can actually skip multiple catalogs with no error or warning message. Since this situation is not easily reproducible, and since Microsoft typically has no interest in fixing unsupported objects, this may be happening in your environment right now
Blogs
Building the Team: Roles and Responsibilities in FinOps
By HeyMo0sh
In my experience, FinOps success has never been just about tools or dashboards. It...
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...
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