Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@molaram when the client isn't responsible for restoring everything when they destroy it all, then they don't get the ability in my books.
-
@C0D4 I'd love to agree or disagree, but I've been working here only for two years. This client has been with the company much longer, and the reason they have admin access to their DB is something I never found out.
-
@molaram Epic automation right there! Good job!
This is how you'd imagine a sysadmin.
(Stolen from Reddit)
Such dedication much wow
Debian sysadmin?
"Hello,
it turns out we probably caused the downtime ourselves. I didn't know dropping 170 databases and deleting 80 entire projects at once could do that"
Gave me a hearty chuckle. Especially as the client adamantly refused to have SSDs installed for the DB to run on top.
Just imagining the poor read-write heads jerking back and forth in vain attempts to find all the data to delete... So yes, dropping 170 databases at once does in fact take a database server down to its knees, as deleting is all the drives will be doing for a while.
At least it wasn't my or my colleague's mistake this time.
joke/meme
sysadmin life
database management