"DB Horror Story: Our SQL Server Just Went Rogue"
So we've got a bit of a situation on our hands - our main SQL Server just went rogue and started writing garbage data to our production tables. I'm talking thousands of rows of nonsensical data that's now causing our reporting system to throw errors left and right. Was anyone else out there ever dealt with something like this?"
So we've got a bit of a situation on our hands - our main SQL Server just went rogue and started writing garbage data to our production tables. I'm talking thousands of rows of nonsensical data that's now causing our reporting system to throw errors left and right. Was anyone else out there ever dealt with something like this?"