 <p>If you did not prepare for this question then there is no build in way to get to that information. However, you could use third party log reader tools to recover (all) the last statements that where executed against the database. This requires the database to be in Full recovery mode. You could potentially go back as far as you have log backups with this method.</p> <p>If you want to prepare for that question being ask in the future, you have several options. The most obvious one is Change Data Capture. You also could write a trigger yourself that records data changes. You could also run a trace capturing SQL Batch Started. Finally you could use a third party network sniffer/logger to capture all statements send to the server (this however requires that connection encryption is not used).</p>