Hi Jugal, Thanks for your article. However i have few doubts on this topic, i really don't know how reasonable they are
Below is what my current log shipping setup.
Primary Server Name: PrimaryServer
Primary Server DB: PrimaryDB
Drives on Primary Server: C,D,E & F
PrimaryDB files location: .mdf(D) & .ldf(E)
Seconday Server Name: SecondayServer
Seconday Server DB: SecondaryDB
Drives on Seconday Server: C,D & E
SecondaryDB files location: .mdf(D) & .ldf(E)
If suppose i created a secondary data file(.ndf) for primary database and kept it in F drive on Primary server.In this case, will the secondary data file(.ndf) be created over there in secondary database located on Secondary server? If so, where it will be created i mean in which drive it will be created?
As you said,
If you choose "Disconnect User Option" - users will be disconnected from the database each time the log shipping restore job attempts to restore a transaction log to the secondary database.
If you do not choose "Disconnect User Option" In this case, the restore job cannot restore transaction log backups to the secondary database if there are users connected to that database. Transaction log backups will accumulate until there are no user connections to the database.
From the second stmt, if suppose users stay connected forever on secondary DB for reporting purpose, then the copy files in copy directory on secondary servers will be committed for a specific threshold hours(let say 72 hours). Next restoration will not be possible though we have t-log backups from past 72 hours, since definitely we will get LSN mismatch error while SQL Agent job attempt to restore the t-logs.
How far the second stmt is correct? What is the use of TUF(Transact Undo File)?