Comments
Sort by recent activity
Problem is now solved. [image] Thanks for all help.
Turns out the problematic database had an unknown and invalid federated table which indeed was impossible to access. However, that table's existence was not known to me. And since the MySQL error message was truncated (by MySQL it turns out, not Redgate, omitting the name of the table), it was only natural to misunderstand it. Due to the perceived poor error reporting capabilities of MySQL, I think it would be very helpful if the Redgate product could echo extra debugging data (such as the name of a problematic item when iterating through the tables, views etc.), instead of simply forwarding the inadequate error output of MySQL. That would make it easier to understand and solve problems of this kind. :idea: / comments
Problem is now solved. Thanks for all help.
Turns out the problematic database had an unknown and invalid federated table which indeed was impossible to access. However, that table's existence was...