Previously in SQL Server 2000, the STOPAT clause was provided for RESTORE LOG wherein you can "halt" the recovery process at a particular point in time. This feature is very useful for recovering from accidental user errors and such.
Now in SQL Server 2005, there is a STOPAT clause provided in the RESTORE DATABASE command also. The first time I saw this option, I was confused and wondered how we can provide a point-in-time recovery with a full database backup - because the full database backup is essentially an image of the database and does not contain the entire log backup (only contains the portion which changed during the backup command itself.) But I never thought about it much after that.
So when a customer asked me how this feature works, I dug in a little bit and here's what I found:
So, STOPAT in RESTORE DATABASE can be a little disappointing if you are not aware of the real purpose of this clause. Please review http://msdn2.microsoft.com/en-us/library/ms191468(SQL.90).aspx which explains this in detail.