Hi,I have a SQL2014 server using high availability. So there is a primary and a secondary.There is a vendor process that pulls allot of the data from a large (5 mil) table every morning. It takes that data into Great Plains digests it and then has to write back to my to the same exact SQL2014 production server. The problem is that when the process starts it seems to putting a lock on the table to pull all the data - which of course creates blocking for my users. This is now a big problem, my users can't work and the application that pulls this data sometimes fails with a pipe error ..not good. This is a procedure locked down vendor supplied process so I don't have much access. We do have some control and I was thinking of having them point to the secondary to pull the data to relieve the pressure off the main DB....but if I have them point to the secondary, they also need to write back to the database which they can't do because the secondary is read only. Could I maybe create a third replica and make that read write?We are willing to create an additional db server if need be, but how to update it back to prod.Not sure of my options here, can anybody think of anything that could help this situation?
↧