Can someone explain how Marketing Cloud locks data in Data Extensions during certain routine operations?
Case A: An email begins sending and midway through, a SQL Query gets ran which overwrites the data extension. In my experience, this causes the mailing to fail, which tells me that whatever lock the send has (if any) is overridden by the SQL SELECT query.
Case B: An email begins sending and midway through, a Data Filter is applied which will similarly overwrite the data extension. Does this function the same was as a SQL Query with Overwrite, or will it wait for the send to complete?
What I'm trying to avoid is a situation where a user is trying to send to one of our sendable Data Extensions while they're being updated. I'm sure I can train users to send outside of update times but I'd prefer to have these foolproof and easy to use, so I'd also prefer not to rely on automations in order to send. Is that something that's possible?