Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Bug in SQL Server 2005 RTM?
Message
De
09/01/2008 00:49:07
 
 
Information générale
Forum:
Microsoft SQL Server
Catégorie:
Autre
Versions des environnements
SQL Server:
SQL Server 2005
Divers
Thread ID:
01279775
Message ID:
01280459
Vues:
33
I think you have to at least choose the last Log backup or both of them, but not only the first one, to get the STOPAT clause generated. At least that's the way it seemed to work for me.

However, I still get errors when I try to run it. Not knowing anything about this particular syntax for restoring a database, I can't off the top of my head figure out what's wrong with the generated statements.

~~Bonnie




>>OK, the Restore didn't run correctly, even though the commands looked ok ... got a few errors, but I may have goofed something up. It's late.
>>
>>Time for me to quit geeking out and think about going upstairs and get to bed, but I'll check back with you in the morning to see if you've gotten any better results.
>>
>>~~Bonnie
>>
>
>Hi Bonnie,
>
>I re-tried all steps at home and the STOPAT clause was not generated again.
>
>Here are my steps, may be something is wrong:
>
>After I created a database and a table, I click on Tasks, Backup. Select database, specify name of the backup and expiration (1).
>
>Then repeat it for Log file.
>
>Then do changes.
>
>Backup log again.
>
>Then select Restore database. Click on the button close to most recent backup and select some time about 2 minutes ago. Check data and first backup file. Then press Script button and there is no STOPAT option in the generated command. The Restore failed, though, saying I have to select STOPAT or NORECOVERY option. But I just did?
>
>Anyway, it was a quick try, I may try it again.
Bonnie Berent DeWitt
NET/C# MVP since 2003

http://geek-goddess-bonnie.blogspot.com
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform