Performance issue with Linked server in UAT environment, but same SQL when run from DEV server performs fine with the Linked server

Application:  Has linked servers to a SQL server and an Oracle server.

Recently a release was moved from DEV to UAT. A job which runs for 10mins in DEV is taking 90mins in UAT.

We isolated the problem to 2 SQL statements, but these statements run fine in DEV, which is also pointing to the same SQL linked server.

The JOB prior to release in UAT used to run in 10mins time. After the release the job is taking 90mins, but the same job runs in 10mins in DEV

Any pointers, I the problem SQL in the job has been identified to be SELECT statements from a VIEW, which in turn points to other views mapped out of the linked server(SQL).

But the same peice of code just runs fine in DEV??? puzzled.
lakshmikatzAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mark WillsTopic AdvisorCommented:
There is a high probability that it is not the SQL code, but the environment around it...

Could be the drivers in UAT compared to DEV - make sure they are the same versions.

Could also be the configuration and networking for UAT compared to DEV.

Could be different security / virus settings where by UAT has very high scanning on all traffic (happended to me once - turned out the protection software was BYTE scanning in uat over the network because it was a different "trust" relationship between dev and production).

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Mark WillsTopic AdvisorCommented:
Also just heard of a production environment where the SAN was upgraded, and they "forgot" to turn caching back on ! Disaster for a few days (investigating everything SQL). There are a lot of environmental factors that can cause grief, trouble is, it tends to manifest itself in the SQL space and hence gets the blame.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.