How To Keep Up with SQL Server
It can be a challenge to keep up with the rapidly evolving SQL Server platform. Andy Warren has a few ideas today.
Call for Speakers - SQL Saturday Pittsburgh
SQL Saturday #440 is coming to Pittsburgh on October 3, 2015. Now is the time to submit if you'd like to speak at the event.
SQL 2014 Clustered Columnstore Index Rebuild and Maintenance Considerations
Building (or rebuilding) a Columnstore index can be a resource intensive operation. In this article, Denzil Ribeiro describes the index rebuild process and index maintenance for clustered Columnstore indexes in SQL 2014.
Detecting Differences in Files on Servers
Detecting file differences on two different web servers using T-SQL.
Download tSQLt Today and Start Unit Testing
The latest version of tSQLt is now available with some SQL Prompt snippets to help you get started.
The Security Payoff
An invitation to hack United's IT systems has resulted in vulnerabilities being found and hackers rewarded for disclosing the issues.
SQL Server Archive and Data Retention Considerations
Tim Smith looks at what to take into consideration before building a design to archive old data in SQL Server databases.
Hiring for Culture
Steve Jones discusses the decision to hire someone that fits in with your culture at work, and what that means.
Stairway to SQL Server Security Level 10: Row-Level Security
Unlike some other industrial-strength database servers, SQL Server lacks a built-in mechanism for protecting individual data records, called row-level security. This stairway level explores why you might want to use such a low-level granularity of data access security and how you can implement row-level security.
Demystifying Oracle's Clustering Factor
One of the more confusing statistics in Oracle is one called the clustering factor. Associated with an index, it's actually dependent on the table data, more specifically the distance between 'jumps' for a given index key. Commonly, a 'jump' is the number of blocks between rows containing the given index key starting with the first block found containing that key. If that sounds confusing don't despair, David Fitzjarrell explains in detail.
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