Is it possible to have secondary server available read-only in a log shipping scenario? -

I'm seeing log shipping in SQL Server 2005 environment. This idea was intended to set log shipping on a secondary server often: Use a secondary server to send the report query, from which the primary DB server is being offloaded.

I came across one on this:

When you create log shipping, you have 2 options. You can configure the log-in lodge operation to be done with the Norwickwari or with standby option. If you use the Norwich option, you can not raise the issue of selected statements on it. If you use the standby option instead of for example, you can run selected questions on the database. When the log file is restored, keep in mind with the standby option, users will be removed without warning by the restoring process. Intensely when you configure log shipping with the standby option, you can also choose between 2 options - kill all the processes in the secondary database and restore the log or if the database is being used log Do not restore. Of course if you choose the second option, the restoration operation can never be run when someone opens a connection to the database and does not turn it off, then it is better to use the option first.

So my questions are:

• Is the above true? Can you really not use log shipping, the way I intend to?
• If this is true, then someone can tell that why can not you run a selection database while restoring the transaction log?

Edit:

The first question is a duplicate but I still want to answer the second question: restores the transaction log Is it not possible to execute the time selection statement?

Can someone tell you why you can not select the selection statement in the database while restoring the transaction log Can you run

The short answer is that the restoration statement is being restored to a special lock database.

writes, I hope there is no need to tell me why they are incompatible with restoring. Why not read this? First of all, there is no way to know that the session that has a lock in any session is read or written. But even if this is possible, a restore (log or backup) is an operation that updates the data page directly into the database. Since these updates go straight to the physical location (page) and do not follow the logical hierarchy (metadata-division-page-line), they will not respect the potential intent of the data from other data readers, and thus change the structures The possibility is as they are read Scan a Select Table After the next-previous indicator the page will be thrown into chaos, resulting in a corrupt read. Ega.