I do not think you can unless you have a good backup of that table. Once you execute a truncate then the server has no log of that event. All of that data is gone. Sorry and I hope that you have a good backup in order to restore from. Truncate is a logged event. All statements which change data within the database are logged. If it wasn't logged in wouldn't pass the ACID test. Please stop telling people that truncate isn't logged. The truncate statement is minimally logged. This means that instead of logging that each row in the table was deleted, a mark is put into the log saying that all records in the table were deleted. In order to restore you will need to restore your database and store the restore at the point when the truncate statement was run. If you do not have log backups restore your most recent full, and differential (if you have diffs). That'll be as good as it gets.

I do not think you can unless you have a good backup of that table. Once you execute a truncate then the server has no log of that event. All of that data is gone. Sorry and I hope that you have a good backup in order to restore from. Truncate is a logged event. All statements which change data within the database are logged. If it wasn't logged in wouldn't pass the ACID test. Please stop telling people that truncate isn't logged. The truncate statement is minimally logged. This means that instead of logging that each row in the table was deleted, a mark is put into the log saying that all records in the table were deleted. In order to restore you will need to restore your database and store the restore at the point when the truncate statement was run. If you do not have log backups restore your most recent full, and differential (if you have diffs). That'll be as good as it gets.