Ashwin:-
I have set up log shipping between two servers named A and B . A is the primary server and B is the disaster recovery as well as secondary server.
The server A is primary server and is both read/write where as the server B is just standby and readonly . The people who are using server B are asking for write access on it as well.
My question is can two servers be read/write while there is a logshipping activated in between ??
conditions:-
server A is the primary server and they dont want people other than the ones already exisiting in the domain to have access to it.
server B is the secondary server and they want the write access to it while the logshipping is on. (they dont really care for the logshipping they just want the access on server B, and also they want to have all the changes made on server A which is possible only through log shipping or replication )
people working with server B has problems with no write permissions on it.
People at server A are not approving of a replication with server B(fearing the changes made on server B might change the actual data on server A).
Is there anything that can be done so that both people at server A and B can have the write access to both servers respectively.
:-
No. In Log Shipping scenarios, the secondary databases only can be queried (read-only) if the database is in Stand-By mode.
If your users need to change data in the secondary database then you should check out Peer to Peer Replication (Enterprise Edition is needed). But you say that changes at the Server B should not be replicated to Server A.
So you need a solution that the data on Server A will be replicated to Server B and users of Server B will be able to update\change that data but the changes are not going to be replicated to Server A. Even if you clone the replicated database on Server B so that your Server B users updates it, how to get the changes that are applied to the replicated database on Server B to that Clone database? Only using some custom methods...
Ashwin:-
Thanks for the prompt Reply Ekrem Önsoy.
But what i am searching for here is a solution for this paricular issue. The server A needs to be logshipped or replicated but a copy of it is to be mainatined.
And the replica which is being maintained(server B) is used to access the originial data for the web application, which is in server A.
The Server A cannot be stand-by since the data is inserted to/changes made to the data are made only to the databases in this server A.
The thing is while the replication or the log shipping is still going good the server B needs to be in a (read/write) Mode . How it can be done?
Be it Logshipping or Replication or any other method of replicating the data the conditions are to be met.
1. Server A should be in sync with Server B.
2. Both the servers need to be (Read/Write)
3. Data in Server B is not changed but a few Stored Procedures might be included in Server B which are optional in Server A.
4. Server A is standard edition and Server B is enterprise edition.
:-
You certainly can not do this using Log Shipping.
Database Mirroring does not work for your situation either.
Merge Replication comes to my mind but I can't be sure unless performing a test. Can you ask this question also in Replication forum? Hilary Cotter or other fellows can tell you if Merge Replication works for your situation or not.
I have set up log shipping between two servers named A and B . A is the primary server and B is the disaster recovery as well as secondary server.
The server A is primary server and is both read/write where as the server B is just standby and readonly . The people who are using server B are asking for write access on it as well.
My question is can two servers be read/write while there is a logshipping activated in between ??
conditions:-
server A is the primary server and they dont want people other than the ones already exisiting in the domain to have access to it.
server B is the secondary server and they want the write access to it while the logshipping is on. (they dont really care for the logshipping they just want the access on server B, and also they want to have all the changes made on server A which is possible only through log shipping or replication )
people working with server B has problems with no write permissions on it.
People at server A are not approving of a replication with server B(fearing the changes made on server B might change the actual data on server A).
Is there anything that can be done so that both people at server A and B can have the write access to both servers respectively.
:-
No. In Log Shipping scenarios, the secondary databases only can be queried (read-only) if the database is in Stand-By mode.
If your users need to change data in the secondary database then you should check out Peer to Peer Replication (Enterprise Edition is needed). But you say that changes at the Server B should not be replicated to Server A.
So you need a solution that the data on Server A will be replicated to Server B and users of Server B will be able to update\change that data but the changes are not going to be replicated to Server A. Even if you clone the replicated database on Server B so that your Server B users updates it, how to get the changes that are applied to the replicated database on Server B to that Clone database? Only using some custom methods...
Ashwin:-
Thanks for the prompt Reply Ekrem Önsoy.
But what i am searching for here is a solution for this paricular issue. The server A needs to be logshipped or replicated but a copy of it is to be mainatined.
And the replica which is being maintained(server B) is used to access the originial data for the web application, which is in server A.
The Server A cannot be stand-by since the data is inserted to/changes made to the data are made only to the databases in this server A.
The thing is while the replication or the log shipping is still going good the server B needs to be in a (read/write) Mode . How it can be done?
Be it Logshipping or Replication or any other method of replicating the data the conditions are to be met.
1. Server A should be in sync with Server B.
2. Both the servers need to be (Read/Write)
3. Data in Server B is not changed but a few Stored Procedures might be included in Server B which are optional in Server A.
4. Server A is standard edition and Server B is enterprise edition.
:-
You certainly can not do this using Log Shipping.
Database Mirroring does not work for your situation either.
Merge Replication comes to my mind but I can't be sure unless performing a test. Can you ask this question also in Replication forum? Hilary Cotter or other fellows can tell you if Merge Replication works for your situation or not.