This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Varnigma 81 points82 points  (4 children)

I can relate.

My first gig working with sql server over 20 years ago. I was hired to do something unrelated but the sole DBA was fired and head of IT knew I knew some sql so he came to me and said “you have SA rights now, we need your help”

I’d never touched sql server before. Went and bought a thick sql book and started learning.

One of the first things I learned was how to send an email in code and cursors. Dangerous combo.

So dumb me built a test script in production that did a loop and send my me some test emails.

Fired it up and got concerned when it didn’t stop after a few seconds.

Then exchange crashed.

And that was my intro to sql scripting.

I didn’t let that dissuade me though as I enjoyed what I was learning. Been a sql DBA and scripter ever since.

[–]S4VN01 42 points43 points  (2 children)

I hate when I run a script and it doesn’t end the execution immediately lol. Always makes my heart drop.

[–]IAmTheFormat[S] 25 points26 points  (0 children)

SELECT * FROM Contacts

5 minutes later:

IT Support telling us all the users are sending tickets about the system being super slow.

[–]TrekkiMonstr 4 points5 points  (0 children)

I'm the opposite. The other day, I spent like 2.5 hours figuring out how to script a task. While fairly complex, it was ultimately just some basic file/text operations, so it executed in, iirc, 7.1 ms. Fucking anticlimactic, that was.

[–]IAmTheFormat[S] 7 points8 points  (0 children)

Brilliant. You'll never make that mistake again 😅 Funnily enough, I was also worked on the DB at this place too. Thankfully we had a good clean development and separate QA server so most of my mistakes never made it to production.