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 |
|
wellmanr
Starting Member
7 Posts |
 Posted - 2007-05-16 : 14:53:16
|
| Hi All!Well if you have read my previous post (just below this one) you know my situation. Now that I have the log shipping working, I have a couple of new questions. I used the sample databases (AdventureWorks and AdventureWorksDW) for my testing with SQL Server. 1. I first used the export wizard to send AdventureWorks (AW) over to my secondary server. The transfer went well. I then used the log shipping wizard on the primary AW to the secondary AW. When the job executed the primary shipped it and the secondary copied it but the secondary would not restore it. The error it shot me was as follows:"The restore operation cannot be proceed because the secondary database 'AdventureWorks' is not in NORECOVERY/STANDBY mode."2. The second database AdventureWorksDW (AWDW) I used the log shipping wizard to not only transfer logs but backup and restore the database over to the secondary. Now, everything works fine with the log shipping, but AWDW stays in (Restoring...) mode. How long will it stay in this mode? Thanks,Ryan******************************SQL - Why are you so much trouble? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-05-16 : 15:43:08
|
| 1. You can't use the export wizard to setup the secondary database. You must either use the log shipping wizard or restore database/log. 2. It stays in this mode until you failover to it.Tara Kizerhttp://weblogs.sqlteam.com/tarad/ |
 |
|
|
wellmanr
Starting Member
7 Posts |
Posted - 2007-05-16 : 15:46:42
|
| Ok.1. That is cool. This one was a test to see if it would work. 2. So there is no way to check to see if the log shipping is working until it has been failed over to?Thanks,Ryan******************************SQL - Why are you so much trouble? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-05-16 : 15:49:37
|
| 2. To see if it's working, verify that all jobs are completing successfully and also look at the log shipping monitor.If you setup the secondary to be a standby database, then it is read-only and therefore you can check if new data is making it to the secondary.Tara Kizerhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
wellmanr
Starting Member
7 Posts |
Posted - 2007-05-16 : 15:54:45
|
| Sweet.Ok. Is this an option that should be set when creating the log shipping job or can I do it now after it has been implemented?Thanks for the patience,Ryan******************************SQL - Why are you so much trouble? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-05-16 : 15:57:49
|
| You have to select that option in the wizard when you are setting it up. You can't go back and make the change now. To fix this, you'll have to start over.Tara Kizerhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
wellmanr
Starting Member
7 Posts |
Posted - 2007-05-16 : 15:59:44
|
| Thanks so much,This job has been a lot of redo's but this may be the final one. I just wanted to make sure I have all the bugs worked out of my plan before I start messing with million dollar databases. Thanks again for your patience and information.Ryan******************************SQL - Why are you so much trouble? |
|
|
|
|
|
|
Secondary DB not in NORECOVER\STANDBY mode