Attach with NoRecovery
For VLDB and Highly Available users with SAN copy infrastructure, the ability to attach a database with NORECOVERY to use as a log shipping target would be a big benefit. This would leverage the SAN copy with the SQL attach capability to quickly initialize log shipping partners.
Upvotes: 13<=-=Apr 18 2007 9:54AM=-=>
Thank you for your suggestion.
This is functionality which we are actively investigating, but cannot commit to at this point.
I will keep you informed as the situation develops.
This suggestion is being closed as a duplicate of another suggestion for the same functionality. Rest assured that the idea is not rejected, we’re just consolidating the work items in our database to make tracking more manageable.<=-=May 14 2007 10:19AM=-=>
Closing as duplicate as previously discussed<=-=May 14 2007 10:20AM=-=>
Item being closed as previously discussed.<=-=Jun 14 2007 10:06AM=-=>
What is the duplicate suggestion this was consolidated into? I want to add that to my watch list.<=-=Feb 4 2009 8:16AM=-=>
Typically the SAN vendors utilize the VDI API layer to coordinate these external backups with SQL Server (BACKUP DB WITH SNAPSHOT…). This creates a header (.bak) file which should contain the necessary log sequence information associated with the backup. Given this header file and the external database device files it should be a trivial matter for Microsoft to provide a CREATE DATABASE FOR ATTACH method that utilizes the header file to restore the log sequencing so that additional transaction logs may be applied.<=-=Feb 4 2009 10:12AM=-=>
This item is currently being tracked as Connect item 270651.