Partitioning in SQL Server - Part 2
Arshad Ali examines the different concepts of partitioning in SQL Server 2012 and provides a step-by-step guide on creating a partition table/index.
Double Counting and Sign Reversals
Make the ad-hoc analysis of identifying potentially double-counted or sign-reversed Accounting transactions simple and painless.
The $50,000 Laptop
The average value of a lost laptop has been found to be much more than you might expect. Steve Jones talks about a recent study.
What Counts for a DBA: Amnesia
Louis Davidson explains why DBAs often need a healthy dose of selective, enforced amnesia about the pain of previous failures.
How Come the Hourglass? Why Database Applications Slow Down
It is frustrating when you hit 'submit' and you get the hourglass big-time. Is it the database to blame? It could be, but there are other suspects that should be considered. Feodor Georgiev describes where, in the long route, to and fro', that a data request makes before returning, that things can get snarled up.
DR Prep
This week Steve Jones asks how you might handle DR preparation or process differently in the new year.
Row Sorting in SQL
It should be easy to model a game of poker in SQL. The problem is, however, that you need to model a permutation from a set of elements. Joe Celko argues that using a group of columns to do this isn't necessarily a violation of 1NF, since a permutation is atomic. Then comes the second problem: how would you sort such a column-base permutation in order? Sorting columns in SQL?
All Flash
Should you think about using SSD storage in your SQL Server databases? Steve Jones thinks this might be something you should consider.
Partitioning in SQL Server
Partitioning has improved with each new version of SQL Server. From partitioned views in SQL Server 7.0 through partition table parallelism in SQL Server 2008. With SQL Server 2012, we are now allowed to even create up to a 15K partition on a single table.
Querying SQL Server Agent Job History Data
Often times we are tasked with having to programmatically come with a list of durations per SQL Server Agent Job to trend the run times and order the results by date. Unfortunately it's not always easy in the way the data is stored in the system tables in the MSDB database. This tip explains how to use the system tables to get the data into the correct format for dates and job durations.
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