First thing, I'm not a SQL expert. I have general knowledge of SQL but it starts to fall away when replication and clustering come into play.
I have a single sql db and associated front-end application in Site A. I have users connecting from Site B to access the the application/db. I'd prefer to have a copy of the db sitting in Sites B for Site B users, the Site A db for Site A users, all while keeping the copy of the db in Sites A & B in synch with each other.
What I'd like to know is can I have the db actively being used in both Site A & B with the add/remove/changes being replicated to the alternate site? I'm not after a fail-over scenario where one db is the master and the other the standby db. They both need to be active.