Enable query log (please pay attention to the performance caveats listed on that page)
Wait for said data loss to occur
Examine query log to see what happened
Profit?
In addition to the above steps, I'd also recommend doing a comprehensive audit of your grants to see what user accounts might have access to this database that shouldn't have access.
Check out aspersa's 'stalk' and 'collect' tools: http://aspersa.googlecode.com/svn/html/stalk.html. Smart use of those should eliminate the need to enable the general query log, which probably gathers way too much data in two weeks to justify.
Other then that: tell us more about your setup: do you run replication? What kind of applications? Who has what kind of access? Do you have any suspects?
In addition to the above steps, I'd also recommend doing a comprehensive audit of your grants to see what user accounts might have access to this database that shouldn't have access.
Check out aspersa's 'stalk' and 'collect' tools: http://aspersa.googlecode.com/svn/html/stalk.html. Smart use of those should eliminate the need to enable the general query log, which probably gathers way too much data in two weeks to justify.
Other then that: tell us more about your setup: do you run replication? What kind of applications? Who has what kind of access? Do you have any suspects?