Mulitple replicas on same db, how bad will this hurt?

I know going in that what I’m about to do is not recommended. What I’m hoping to get is some understanding of where the risks are and how bad I might muck things up.

Scenario.

Two servers: Inside and Portal.

Db on Inside contains data for mulitple customers. Reader fields not implemented since we don’t need that kind of security in house.

Each customer wants access via the Portal server to their stuff.

I have created two replicas of the Inside be on the Portal, each using a selection formula to push out only items belonging to each customer.

User has read only access to the Portal dbs, each db has an ACL that precludes access by the ‘wrong’ customer.

Portal dbs don’t replicate anything back inside.

Since the replication formulas include restrictions on which customer’s data goes where, there seems to be little risk that the two dbs on the Portal will transfer data between each other.

It all sounds like it should work…now, burst my bubble and tell me what could go wrong (and how likely that might be) and if there’s anything else I should do or watch to keep myself out of too much trouble.

TIA for the assist.

Doug.

PS - additional servers are not an option…

I’ve searched this forum and not found anything directly related to this so links to information are appreciated.

Subject: Mulitple replicas on same db, how bad will this hurt?

What could go wrong is that the Portal server starts to replicate with itself, and thereby replicating the two different customer DB’s with each other.

I would have gone with reader fields and roles/groups to make sure that, internally, anyone can read anything, but that the customers can only read their own docs. It would also be easier the day you need to expand the # of customers.

$0.02

/Peter