I will do my best to explain the situation and what I am trying to achieve.
My company provides live data during sports events and with hiring more data entry employees comes more locks on our database. We have a team that enters data as the sporting event is happening and another team that "publishes" this data onto a website. Problem is during busy times during the "publishing" important tables get locked and slow down the saving of events done by the data entry team.
We have determined that maybe there are too many hands in the pot and we will replicate between two databases so the data entry team saves on DB1, that is replicated to DB2 and the "publishing" hits DB2. Which could help but I feel that during the replication process the tables will still be locked and I still have the same problems.
I have more then capable hardware and open to all suggests and what the best practice might be. Is this my best option and hope for the best?