March 3, 2014 at 2:46 pm
I have to set up a development database that is a real time, or near real time, copy of our production database for our developers to hit. One of our front end applications needs a block of t-sql run each time a restore happens. I am new mirroring and log shipping, but both don't seem viable due to the fact that the DB needs to be online after a restore, and then I have to run the block of sql code each time the restore happens. Any ideas or areas that I can research? Its a SQL 2008 R2 environment. thank you.
March 3, 2014 at 2:57 pm
That block of T-SQL is read-only or Read\Write ?
--
SQLBuddy
March 3, 2014 at 3:00 pm
Thanks for the quick reply! I actually run one line of code that calls sp_change_users_login so I guess it would be read/write
March 3, 2014 at 3:12 pm
Yeah it's R\W operation. LS or DB Mirroring doesn't help in this scenario.
Your only option would be replication. But that's not designed for entire DB replication.
If the requirement is not really online, then you can use Backup\Restore safely.
--
SQLBuddy
March 4, 2014 at 8:15 am
If it has to be near real time, replication or an availability group (2012 and greater) are your only real options.
By the way, this is a 2014 forum. If people don't notice that you're talking about a 2008 server, you might get answers that aren't applicable to you.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply