As a part of audit we may be forced to lock SA ID.In that scenario what would be the impact of locking SA ID on primary and replicated ASE?
In what scenarios, replication server needs SA id of Primary and replicated ASE.
Is there a way to get around this(e.g. by creating another id for same use)?
I suppose you can create a sa role , create a new user and grant sa role to the new user.
new user would have all the permissions the normal sa user will have.That may solve a bit.
I could not help much though.I have limited knowledge about Sybase Replication Server.
Thanks,
Nag
(09-18-2009 03:38 AM)Nagendra Wrote: [ -> ]I suppose you can create a sa role , create a new user and grant sa role to the new user.
new user would have all the permissions the normal sa user will have.That may solve a bit.
I could not help much though.I have limited knowledge about Sybase Replication Server.
Thanks,
Nag
Hi Nagendra,
Thanks for replying!! But I am more concerned about Replication server as it needs sa id password to be same across replication server and Primary and replicated ASE.
NOTE: for ASE there is a document on Sybase site with all the detail step listed