@SQLTrooper@GavDraper@kevchant Thatโs why the query on the replica is super slow. I will reconfig the replication tonight to make sure itโll bring the indexes over. Thanks again for all your help! ๐๐ค
We have 2 servers. (1) is the SSRS Report Server, (2) hosts all the data. I truncated the log on (2). After that all the reports slow down, some of them timeout and crashed. I can run any the reports from VS locally. Please help, itโs been a week our reports not working #sqlhelp
@SQLTrooper@GavDraper@kevchant Hi everyone, thank you very much for your help. I compare the execution plans on 2 servers and found out the replica doesnโt bring over all the NC indexes.
@GavDraper@SQLTrooper@kevchant And I tried to recompile 1 proc that use to generate 1 report. @GavDraper I agree with u itโs para sniffing. I also checked the time report rendering, it takes a lot of cpu to render just 1 report.
@GavDraper@SQLTrooper@kevchant Our system admin has a snapshot of our report server and the plan was to rollback to 3 weeks ago when everything was running fast. It didnโt get any faster after the switch, so he changed it back to where we were.
@GavDraper@SQLTrooper@kevchant Hi I ran the query without recompile took 37 sec to complete. With option recompile it took 34 sec. What does it tell you?
@GavDraper@SQLTrooper@kevchant Thank you! My thought exactly just bad timing. The reports just started to slow down right after I truncated the log and rebuilt the replication. Will do it now and let you know. ๐
@SQLTrooper@kevchant@GavDraper Thank you. I have a dumb question if thereโs a possibility thatโs because of me truncating the transaction log on the db (on server 2) that the report server (server 1) query to cause the slowness on the reports?