Unanswered: Best way to copy-over (split and maintain) a Stand-by database?
I have a quick question about migrating stand-by databases.
I have a stand-by database that I maintain on a Sql Server 2005 instance >> I grab transaction log files everyday (from another server) via SFTP, and then consequently apply said log files to my aforementioned stand-by database to keep it up-to-date.
Today I was told that we need to move a copy of said stand-by database to another Sql Server 2005, server BUT I don't want to have to rebuild this stand-by database from scratch >> (restoring a full back-up from 2 months ago and then re-applying a gazillion transaction log files to bring us up to speed)....
So my question is, what is the most efficient way to copy over my stand-by database without losing the LSN sequence number (in transit), so that I can continue (or "start" for the new server) to apply transaction log files to both Sql Servers without losing a step?
Someone suggested detaching and re-attaching the DB, but I'm not yet positive if this will work...
off top of head others may want to comment about this
why stop the SQL
copy the SQL files to a other place on server same server
stop the stand-by server
copy the newly copied file to stand-by server
start the stand-by server
hope this help
See clear as mud
the aim is store once, not store multiple times
Remember... Optimize 'til you die!
Progaming environment: Access based on my own environment: DAO3.6/A97/A2000/A2003/A2007/A2010 VB based on my own environment: vb6 sp5 ASP based on my own environment: 5.6 VB-NET based on my own environment started 2007 SQL-2005 based on my own environment started 2008 MYLE YOUR PASSWORD IS JUST LIKE YOUR TOOTHBRUSH DON'T SHARE IT.