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 |
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
 Posted - 2005-04-15 : 11:10:39
|
I've just started delving into this.I've got a wizard do a VERY simple log ship for a test database (VERY SIMPLE - 0 tables  ) - that is working fine.Now I've added my first table - and it seems that my beliefs are correct - i.e. table creation is not an operation than can be re-created via the "log" part of log shipping - a new full backup will be needed. Correct?FYI - this is a proof-of-concept (which I need to finish by Wednesday  )at the moment, with the idea being to sue Log Shipping to create a reporting environment, and not a warn-failover environment...CiaO 4 now - and have a great weekend*##* *##* *##* *##* Chaos, Disorder and Panic ... my work is done here! |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-04-15 : 13:59:35
|
| Log shipping can not be used for a reporting environment as each time that the tlog is applied to the standby server, all users will be disconnected so that it can be applied. You should look into replication for a reporting environment.Your log shipping isn't working if you can't see the new table on the standby server as DDL is logged. I just tested this in a production environment by creating a test table on the primary server, ran the tlog backup on the primary server, then ran the copy and restore jobs on the secondary server. I was able to see the new table in the secondary server. Check the log shipping monitor for the status of log shipping.Tara |
 |
|
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
Posted - 2005-04-18 : 04:46:59
|
| Thanks Tara,We are aware of the log shipping disconnects, but since our production data is a combinations of in-house and 3rd party data stores (against which we cannot set up replication, due to th GUID), we are contrained by what we can do. Currently, we are using a custom-written version of log shipping as a legacy from the SQL 7 days, and it is unstable, and no-one here has any IP on it, hence the drive to try and replace it with MS's work, rather than try and fix it (that remains our 2nd options, the 3rd one being to do my own custom version :-) )*##* *##* *##* *##* Chaos, Disorder and Panic ... my work is done here! |
|
|
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
Posted - 2005-04-18 : 04:51:55
|
| Hmm - on the other point, it does seem that I must have somehow set it up incorrectly - although using a wizard, I would have thought that shouldn't have happened. Time to go and dig into the logs and see what there is to see...as far as I can see, it can't be missing a T-Log, because obviously then we would have had failure of further restore jobs. Strange..*##* *##* *##* *##* Chaos, Disorder and Panic ... my work is done here! |
|
|
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
Posted - 2005-04-18 : 07:55:43
|
| Found my mistake - errors in log shipping UNC directory - Transaction Lgo backups weren't being found and copied.*##* *##* *##* *##* Chaos, Disorder and Panic ... my work is done here! |
|
|
|
|
|
|
|
|
SQL Server Log shipping