Yeaaahhhh any competent DBA would be crucified for doing physical deletion nonchalantly in an actual corporate environment…
Due to integrity issues within one database or across several ones in complex chains.
Honestly a lots of the times logical deletion is preferred anyway. And then that deletion request would be propagated via events and then, maybe, possibly physically deleted.
What’s the point in those over simplifications ? Makes dba looks lazy imho which isn’t a nice thing to do.
Any halfway competent DBA could delete it from live databases easily. Your account is going to have a unique identifier.
It’s usually done for compliance purposes regarding data retention.
Yeaaahhhh any competent DBA would be crucified for doing physical deletion nonchalantly in an actual corporate environment… Due to integrity issues within one database or across several ones in complex chains. Honestly a lots of the times logical deletion is preferred anyway. And then that deletion request would be propagated via events and then, maybe, possibly physically deleted. What’s the point in those over simplifications ? Makes dba looks lazy imho which isn’t a nice thing to do.