June 27, 2007 at 10:56 am
Has anyone worked with setting up Transactional replication on a PeopleSoft db, which by default all their tables do not use Primary Keys? I would like to change all the unique clustered indexes to PK's, but "it's PeopleSoft", so our developers don't want to mess with it. I would also be open to a third party product that could make transactional replication work. Any answers greatly appreciated - Thanks!
June 27, 2007 at 11:37 am
SQL Server Transactional replicattion *requires* primary keys, Period.
You could try to use DB mirroring but I am not sure it fullfil your needs, Do you need the replica as a Reporting server ?
* Noel
June 27, 2007 at 11:41 am
Unfortunately the reporting db we are trying to host with replication needs to be a r/w db as the PS app needs to write to its own system tables to generate reports. We were also planning on doing setups on the reporting db differently to allow more reporting/querying through the app, which will require write access to the PS system tables.
June 27, 2007 at 11:47 am
I know the feeling. Sorry you have to have PKs or use Merge but Merge is probably too intrusive for PS
* Noel
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply