SQL Server - Can I surgically remove a bad cached query plan or am I chasing the wrong idea? Specifically the isolation level is set to serializable within the hibernate layer which I have learned is not optimal for high volume production environments. A contributor to the problem is found within the application servers.Through a lot of pain, I've determined that the time outs Normally these queries take 4 toġ0 seconds. The root problem is that queries coming from an application serverĪre taking longer than 60 seconds.I mentioned that I do have other posts all related to this topic. So given the above - is this option actually used in the real world? Is it acceptable that I recommend (and test) this as an option for a production environment? Two queries run at the same time could swap There have been at least two serious bugs in the past related to.But I need to know whether this is a really bad idea before I try.
Wait are you certain OPTION (RECOMPILE) is the answer? The same query and parameter run via a local stored procedures executes in less than a second.These queries take minutes to complete and cause heavy impact. ETL Queries that cause clustered index scans when run through the ssis agent.
These queries are executed (to the best of my knowledge) sequentially and at scheduled intervals. I have a DBA who, so far, is not a fan of the idea of OPTION (RECOMPILE) within the meat of Report ETL ssis agent queries. This option seems to get a lot of bad press. Is OPTION (RECOMPILE) used in production?
0 kommentar(er)
