Here's how I would do this. I always write it as a select first to verify I get the rows I want to delete. Then just comment out the select...

Another thing to consider. As a production DBA you will most likely have to be on call.  3am calls... weekend calls.  Maybe you're in a big company and you get...

No matter which path you choose if you want to be good at your job you will need to dedicate a portion of your free time to study and practice...

You're title reminds me of a quote from one of my favorite authors Larry Winget... "You're success is your own damn fault!"

But I'm with you on the burn...

Good question. I recently found myself researching that Precision, Scale and Length page to figure out why some division kept giving me extra zeros at the end of the number. ...

Nice. I started learning Python but then needed to do more C# for work so I dove into that. This looks like a good reason to pick back up with...

Move to FL and just wear flip flops... problem solved. :hehe:

Works in SSMS 2014 as well.

Depending on what you're trying to do you could use two columns. One with the date formatted as a string the way you want to display it and another with...

Hahaha... who knew there were so many SQL T-Shirts.  :w00t:  That's cool. I might have to get some of those.

As a side note, storing values like that in comma separated list is a poor design. If you have control over the design then void it.  Here's a good book...

You could normalize it with this:

WITH CTE AS
(
SELECT id
    ,LTRIM(RTRIM(m.n.value('.[1]','varchar(8000)'))) AS value
FROM
(
SELECT id
    ,CAST('<XMLRoot><RowData>' + REPLACE(value,',','</RowData><RowData>') + '</RowData></XMLRoot>' AS...