from the same guy that altered a table without warning: deleted a stored procedure without telling anyone

I think someone should show him the exit…

@athlon then the person who hired them should “disappear” next lol

Why store procedures at all? Did you ask yourself: “does this bring joy to me?” Stop hoarding procedures!!! :^]

stored procedures should be deleted, IMHO.

but it was still wrong to not invite you to celebrate that event.

We should not be afraid of mistakes because we learn from them. I make mistakes all the time, so I'm constantly learning. Now I'll deploy to the active slice instead of deploying to the inactive and toggling; let's see what I learn.

@ScribeOfGoD "under puzzling circumstances"

@tosensei it broke several scripts that called that procedure

@darksideofyay well, those should've obviously been eliminated and replaced first.

@NoMad sudo rm -rf employee_name lol

@NoMad "To shreds", you say?

@localpost I was more going for "no conclusive evidence of a suspect was found. The search continues." kind of news report.

The SPROC was in source control, right? (Says the person that has never seen a properly implemented SQL Code Source Control - I know they exist, somewhere out there)

@fiftyhz we don't have a properly implemented anything, we do it like this because maintenance would be a nightmare if we had separate scripts in different places.

@darksideofyay yep, I hear ya. Same issue where I used to work where we had thousands of stored procs. We tried to implement two different source controls - even went as far as trying some of the Red Gate stuff that will monitor the database and put things back to the source control version if they are changed directly on the database. Everyone hated it so we stopped.