Home Forums SQL Server 2008 SQL Server Newbies Job getting stuck in UAT but runs fine in Prod RE: Job getting stuck in UAT but runs fine in Prod
December 8, 2017 at 8:03 am
Jeff Moden - Friday, December 8, 2017 7:49 AMcoolchaitu - Friday, December 8, 2017 7:42 AMArsh - Friday, December 8, 2017 7:37 AMIs the infrastructure(Memory/Processors etc.) for UAT at the same level as for production ? If at lower level , this can also be an issue.The versions are different. Could that be a reason. Execution plans vary, correct
Versions of what? SQL Server? If so, I strongly recommend that you bring the UAT box up to the same level of SQL Server as the Production box. If the UAT box is at a higher level, then you should either role it back to what the Production box is or, better yet, bring the Production level up to the latest SP and CU (it's important for security, as well).
Thanks Jeff