I have a question about SQL Server Log Shipping:
I have set up a log shipping between two databases on two SQL Server instances (SQL 2008 R2).
It has been working with no issues - every transaction is being replicated from the primary to the secondary instance in terms of minutes - all log shipping jobs are running successfully and on time.
Then I decided to test this with DDL, namely creating a new table in the primary instance.
I was surprised to see that 3 days later the table is still not showing up in the secondary database!
Log shipping is running and jobs are running as scheduled with no issues.
I was under the impression that log shipping creates an exact copy of the primary on the secondary and every transaction, DML OR DDL (created objects) will also be replicated.
Why then I do not see the newly created table from the primary to be replicated to the secondary?
What am I missing? Is there an option in LS to tell the process to also replicate objects, schema changes etc?
Please help with information or specific sources of information on this mystery :-)
P.S. Please refrain from questions like "Why are you using Log Shipping when...." and "Why don't you use this and that instead...". I am aware of the alternatives of database replication, in fact I have tested at least 9 other alternatives (SQL Server Replication, Backup/ Restore, CDC, Database Mirroring, Custom ETL etc). I am using Log Shipping because I have a reason to use it and cannot use any other method in this specific case>