DallasDBAs.com

Explaining SQL Server in plain english

Header Right

TSQL2sday

T-SQL Tuesday 121: The Gift of the Dream Job I Didn’t Know I Wanted

by Leave a Comment

T-SQL Tuesday is a monthly blog party for the SQL Server community. It is the brainchild of Adam Machanic (b|t) and this month’s edition is hosted by Mala (b|t) who has asked us to write about “Gifts received this year.” One idea given to write about was “landing a job you never thought you would,” which is perfect for me.

If you’ve followed my story, you know that I’m pretty new to the DBA world. I’m a retired worship leader who’s lost his voice and went home to work side-by-side with his wife in a graphic/web design biz. As I watched that business go through an extended downturn, I attempted to add photography services and grossly underestimated how saturated the local market was. In desperation for meaningful employment I reached out to my friends for help and referrals.

Kevin stepped in and offered a trial period as a DBA apprentice at Dallas DBAs and I’ve never looked back.

Why has becoming a DBA been such an amazing gift? Here are a few of my top reasons.

  • I get the opportunity to learn new things daily.
  • I get challenged by this role a great deal. That makes jobs enjoyable for me.
  • I get a steady income that brings stability and is allowing my family to build a new house in order to foster/adopt more kids.
  • I get to work from home and share an office with my wife—my favorite person in the world.
  • I get to work with my best friend, Kevin.
  • I get to ride my bike way more often than if I worked out of the house.
  • I got a new bike for Christmas as a direct result of this job.
  • I get to ride bikes with Kevin.
  • I get to continue working and serving at our church, which I love.

I could probably go on and on, and I fully expect being a DBA to continue to offer challenges and rewards in the year ahead!

T-SQL Tuesday 121: Gifts

by Leave a Comment

T-SQL Tuesday is a monthly blog party for the SQL Server community. It is the brainchild of Adam Machanic (b|t) and this month’s edition is hosted by Mala (b|t) who has asked us to write about “Gifts received this year” – which is appropriate for the last month of the decade!

So…many…gifts!

Aside from faith, family and friends which are the truest gifts in my life, I had a fantastic year, SQL Server-wise.

In somewhat order:

  • Dallas DBAs is doing very well and will hit a record for sales in 2019!
  • We hired Jeff and he’s been great…
  • SQLDork continues to contribute and learn every afternoon…
  • Got to go to Summit again this year!
  • SQL 2019!
  • New clients helping me pay Jeff and the Dork…
  • Ellipses, bullet points and exclamation points went on sale…!
  • On-site sponsor at SQL Saturday Cincinnati, Dallas and Austin!
  • Existing clients that trust us with their data and projects…
  • 2 freelance DBAs that I can offload small projects to!
  • New prospects for 2020!!!

I could go into lots of detail on each…but nah…go read some more T-SQL Tuesday posts!

Thanks for reading!

Kevin3NF

T-SQL Tuesday 121: Gifts received for this year

by Leave a Comment

T-SQL Tuesday is a monthly blog party for the SQL Server community. It is the brainchild of Adam Machanic (b|t) and this month’s edition is hosted by Mala (b|t) who has asked us to write about “Gifts received this year”

Over the last year or so I’ve attended several NTSSUG meetings on various topics, with various forms of food provided (usually pizza). Most of the time there’s more than enough leftovers to justify taking home an entire spare pizza, which I’d call a win.

Ed.: Yes, of course things were learned, people were met, networking happened and friends were made…but hey….free pizza is free pizza!

/*Please work*/,

SQLDork

T-SQL Tuesday 120: What Were You Thinking?

by 2 Comments

T-SQL Tuesday is a monthly blog party for the SQL Server community. It is the brainchild of Adam Machanic (b|t) and this month’s edition is hosted by Wayne Sheffield (b|t) who has asked us to write about “What Were You Thinking?” – things we have seen that left us scratching our collective noggins.

The list is long, so I’ll just go with something I saw yesterday.  And in September. Both created by a full-time DBA at a client.

BACKUP LOG MyDatabase
TO DISK = 'E:\SQLBackups\MyDatabase.trn'
WITH INIT

Yep.  It runs hourly.  And initializes the .trn file each time. Goodbye Point in Time recovery.

Ick.

Bonus points: Duplicate indexes, which I will cover in a future post.

Thanks for reading!

Kevin3NF

TSQL Tuesday: Changing your mind

by Leave a Comment

 

T-SQL Tuesday is a monthly blog party for the SQL Server community. It is the brainchild of Adam Machanic (b|t) and this month’s edition is hosted by Alex Yates(b|t), who has asked us to write about “Changing Your Mind“

My best technical example of this is something I wrote about in January 2017, so I invite you to read the original post:

PowerShell for DBAs – why I changed my mind.

In addition to the 2 main reasons I gave then, I am adding a 3rd:

dbatools.io has become a very solid and almost all-encompassing way to manage SQL Server and will be a required skillset in 3-5 years at any large SQL shop.

That’s it for this month!

Thanks for reading!

Kevin3NF

T-SQL Tuesday: Your Fantasy SQL Feature

by Leave a Comment

T-SQL Tuesday is a monthly blog party for the SQL Server community. It is the brainchild of Adam Machanic (b|t) and this month’s edition is hosted by Kevin Chant (b|t) who has asked us to describe “Your Fantasy SQL Feature“. (This is also the first time I’ve made a blog post for T-SQL Tuesday.)

The Problem: As a junior DBA, part of my job involves checking job failures for 2-3 clients each day, which we have a script in-house for. Every once in a while, a job actually fails! So like any DBA who knows that you can go to the Job Activity Monitor under the SQL Agent to view details on job history, i do exactly that only to find it’s a job that ran an SSIS package and gave me this very informative error message:

That’s super helpful, thanks!

So now i have to:

  • Check the step properties
  • Look at the path for the SSIS package
  • Drill down into the integration services catalogue
  • clickity, clickity
  • Wait which folder was it in?
  • Go check the path again
  • clickity clickity
  • There’s 12 different packages with very similar names:

  • Resize the window or scroll over to see which one i care about
  • Finally, open the All Executions Report to get a very helpful error message:

Gee darnit, i’m out of coffee.

The Solution: Just put a button in the failure message/job history that does all that for you.  Or a hyperlink. Whatever.

Kevin Hill (b|t) has made a script that reads the SSISDB tables, but often takes a while to run with only the existing Microsoft indexes. Especially if you are keeping crazy amounts of history…like the MS default 365 days, on a busy system.

/*Please work*/,

SQLDork