Hello, I have setup a Transactional Pull replication for an OLTP application which was working fine until I created another publication of the same database. Another team requested for the replicated copy with a different article list. So I decided to create a new publication for them. I was able to set up two publication successfully. However, post that the tester complained that the part of application that uses the replicated copy is working slow. setup - Distributor and Subscriber are on same server. Main Application - Database acts as a Publisher. Few features of the application are pointed to the replicated copy for better performance as they are for fetching huge select queries results(This section has started running slow). Other Team - uses the 2nd publication and have their subscriber on a different server. I have never worked with Replication having two publisher for the same DB. Can anyone suggest me if the slowness is due to having more than one publication. Is this expected?
No. I've had more than one publication on a database before and it didn't cause access to that database to be slow. You'll have to get more details to take a guess at what might be causing the slow-down. I'd suggest capturing wait statistics to see what is causing things to slow down on the server in general. Also look for blocking processes and resource contention in running queries. You may also want to put extended events to work to capture query metrics to see which queries are running slow and why. But without a lot more info, that's the only advice I can supply.