Transactional replication or log shipping would be your options.
Log shipping is easier to set up, but users will have to be kicked out when a new log is applied.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We have 2 servers, one with standard edition and one enterprise edition of SQL Server.
We would like a couple of databases in the standard edition be replicated (for read-only purposes) into the 2nd server with the enterprise edition.
Given the current licenses, what's the best method to achieve that especially if we want it to be a real-time or near-real time replica?
Transactional replication or log shipping would be your options.
Log shipping is easier to set up, but users will have to be kicked out when a new log is applied.
Hi VivekD-8637,
In addition, by default, Subscribers to transactional publications should be treated as read-only, because changes are not propagated back to the Publisher. However, transactional replication does offer options that allow updates at the Subscriber.
For log shipping, the secondary database may be in either the RECOVERING state or the STANDBY state, which leaves the database available for limited read-only access. But database can’t be read when you’re refreshing data, you must kick out any users as Erland mentioned.
Please refer to Transactional Replication and Log Shipping which might help.
Best Regards,
Amelia
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread