Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
gwhiz
Yak Posting Veteran
78 Posts |
 Posted - 2008-04-08 : 18:15:23
|
| Here's one I'm having some issues with. We currently use log shipping in 2000 to our remote site we also have a performance testing environment in that same remote site. In SQL 2000 we are able to stop SQL Server and copy the mdf and ldf files and then attach them else where to perform our testing. They seem to have "improved" the process in SQL 2005 by no longer allowing us to attach databases in a loading state. Any ideas on a way around this. The main reason we are trying to do this is because our database is very large ~1.2 TB and moving a backup file across the WAN is not a very attractive option. We looked at using database mirroring but the problem with that is the lack of compression while syncing the data.Mike Bliesner |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-04-08 : 18:37:02
|
| So what is the requirement? Does your requirements need real-time data sync between two site? How far is remote sites? How high is transaction rate in Primary servers?Answer this, then we can help you with recommendation? |
 |
|
|
gwhiz
Yak Posting Veteran
78 Posts |
Posted - 2008-04-08 : 19:14:56
|
| The requirement is that we have a performance testing environment at a remote site 300 miles away and we need to get a copy of the production environment to use for testing we need to refresh the data at frequent intervals. With SQL 2000 we were able to accomplish this quite nicely by using SAN Cloning of the log shipped database. But we can no longer do this since in SQL 2005 we can no longer attach databases that are in a loading state. |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-04-08 : 19:25:14
|
| We were able to transfer 650GB files in 20 hours using FTP (900 miles apart). You should look for compression tools like SQLlitespeed,Redgate.SAN cloning should be really expensive. |
|
|
|
gwhiz
Yak Posting Veteran
78 Posts |
Posted - 2008-04-08 : 19:29:27
|
| 20 Hours is too long. We currently refresh the environment 2-3 times a week. We are using SQL Litespeed for the logshipping to our Disaster Recovery server. I guess what I'm really looking for is there a trace flag we can turn on to enable us to attach databases in a loading state similar to what we were able to do in 2000 |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-04-08 : 23:17:32
|
| Don't think so. |
|
|
|
|
|
|
Attaching a logshipped database