If you're really adventurous (and the relevant log is still around, either in the active log or in a backup), you can get some information like that from the transaction log.

See here[/url] for an example of how to do this.

Having said that, you'll have to do some work to tie the rows in question to the correct operation in the log, and even then you'll only have the SID for the SQL Server login (so if multiple people have access to that login you won't have gotten too far, for example).

Like Gail said, no way around proper auditing for something like this.