The 12 days after release

3

December 24, 2013 by Kenneth Fisher

On the first day after release my developer gave to me

  • a performance problem on a crucial query

 

On the second day after release my developer gave to me

  • 2 deadlocked queries
  • and a performance problem on a crucial query

 

On the third day after release my developer gave to me

  • 3 failed backups
  • 2 deadlocked queries
  • and a performance problem on a crucial query

 

On the fourth day after release my developer gave to me

  • 4 secondary replicas
  • 3 failed backups
  • 2 deadlocked queries
  • and a performance problem on a crucial query

 

On the fifth day after release my developer gave to me

  • 5 missed permissions
  • 4 secondary replicas
  • 3 failed backups
  • 2 deadlocked queries
  • and a performance problem on a crucial query

 

On the sixth day after release my developer gave to me

  • 6 indexed views
  • 5 missed permissions
  • 4 secondary replicas
  • 3 failed backups
  • 2 deadlocked queries
  • and a performance problem on a crucial query

 

On the seventh day after release my developer gave to me

  • 7 schema changes
  • 6 indexed views
  • 5 missed permissions
  • 4 secondary replicas
  • 3 failed backups
  • 2 deadlocked queries
  • and a performance problem on a crucial query

 

On the eighth day after release my developer gave to me

  • 8 gigs of ram
  • 7 schema changes
  • 6 indexed views
  • 5 missed permissions
  • 4 secondary replicas
  • 3 failed backups
  • 2 deadlocked queries
  • and a performance problem on a crucial query

 

On the ninth day after release my developer gave to me

  • 9 stored procedures
  • 8 gigs of ram
  • 7 schema changes
  • 6 indexed views
  • 5 missed permissions
  • 4 secondary replicas
  • 3 failed backups
  • 2 deadlocked queries
  • and a performance problem on a crucial query

 

On the tenth day after release my developer gave to me

  • 10 sparse columns
  • 9 stored procedures
  • 8 gigs of ram
  • 7 schema changes
  • 6 indexed views
  • 5 missed permissions
  • 4 secondary replicas
  • 3 failed backups
  • 2 deadlocked queries
  • and a performance problem on a crucial query

 

On the eleventh day after release my developer gave to me

  • 11 urgent pages
  • 10 sparse columns
  • 9 stored procedures
  • 8 gigs of ram
  • 7 schema changes
  • 6 indexed views
  • 5 missed permissions
  • 4 secondary replicas
  • 3 failed backups
  • 2 deadlocked queries
  • and a performance problem on a crucial query

 

On the twelfth day after release my developer gave to me

  • 12 CPUs
  • 11 urgent pages
  • 10 sparse columns
  • 9 stored procedures
  • 8 gigs of ram
  • 7 schema changes
  • 6 indexed views
  • 5 missed permissions
  • 4 secondary replicas
  • 3 failed backups
  • 2 deadlocked queries
  • and a performance problem

    that we finally solved!

 

3 thoughts on “The 12 days after release

  1. Carla Abanes says:

    funny, i was singing it in my mind while reading it hahaha merry christmas to you!

  2. Hi,
    I am facing more dealock issues in production database.Please advise how to resolve the deadlock issues..please

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Enter your email address to follow this blog and receive notifications of new posts by email.

Join 1,671 other followers

Follow me on Twitter

ToadWorld Pro of the Month November 2013
%d bloggers like this: