Sorry for the wonky title if it got you confused.
I want to know if a server can be a slave and master at the same time. Our problem is that we have lots of mobile units that need to be synced to the master but they only need 6 out of the 100s of tables on the master. All the extra tables serve no purpose on the slave except for delaying synchronization and adding data costs.
Server A: Master to Server B.
Server B: Slave to Server A, Master to Server C.
Server C(n): Slave to Server B.
Server A: masterSchema, slaveSchema.
slaveSchema is a sync'd subset of masterSchema.
Server B(n): Slave to Server A.slaveSchema
If the answer is no would anyone have any alternate solutions to propose. We're trying to avoid having to sync the different schemas/databases manually as that can get real ugly real fast. We have a lot of critical live data flying around so both performance and integrity are of concern.