Here is one way to solve your problem:1. Create a new database, name it something like DatabaseName_2.2. Perform your recovery on DatabaseName_2, you will have to use the command line to do this, as the gui doesn't seem to be able to handle a restore from the catalog to a different database.3. Copy the pertinent data back to your live database. 4. Drop DatabaseName_2 since it is no longer needed.You might also want to look into a tool called log explorer (http://www.lumigent.com/products/le_sql/le_sql.htm) from lumigent.Also, Here is what the command line recovery code might look like.-- Begin recovery operation with the NORECOVERY argumentRESTORE DATABASE DatabaseName_2FROM DISK = 'c:\Program Files\Microsoft SQL Server\Backup\DatabaseName\DatabaseName_db_200311200131.BAK' WITH MOVE 'DatabaseName_Data' TO 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\DatabaseName2_Data.MDF', MOVE 'DatabaseName_Log' TO 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\DatabaseName2_Log.LDF', NORECOVERY , replace RESTORE LOG DatabaseName_2 FROM DISK = 'c:\Program Files\Microsoft SQL Server\Backup\DatabaseName\DatabaseName_tlog_200311200200.TRN'WITH MOVE 'DatabaseName_Log' TO 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\DatabaseName2_Log.LDF', NORECOVERY, replace -- Play the final log, with the point in time to recover to, and with RECOVERY enabled RESTORE LOG DatabaseName_2FROM DISK = 'c:\Program Files\Microsoft SQL Server\Backup\DatabaseName\DatabaseName_tlog_200311200300.TRN'WITH MOVE 'DatabaseName_Log' TO 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\DatabaseName2_Log.LDF', RECOVERY, replace,STOPAT = 'Nov 20, 2003 2:56 AM'
Of course names, locations, times, etc will be different. You should get the basic idea from what I have posted and in BOL.-ec