How do I fix a Query fails on linked server

SCENARIO:
I have 3 SQL Servers running: SERVER A, SERVER B, SERVER C

A table on SERVER A where trigger a INSERTS data on SERVER B and then calls Stored Proc (SP) on SERVER B.

The SP on SERVER B updates that same table with data retrieved from SERVER A and SERVER C. This is where it fails.

If I copied both tables to SERVER B the SP executes successfully... So I know the syntax is correct.
The problem occurs when and ONLY when I attempt to UPDATE the table on SERVER B with the join that links back to SERVER A.  Any ideas.

In Visual studio or enterprise mgr. and do the single query to that table it passes the results.
LIFEEXPERTAsked:
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.

David ToddSenior DBACommented:
Hi,

My first thought is that htere is too much happening in one trigger firing.

That is, calling a stored procedure on another server is holding an implicit transaction too long, so this is likely to not scale well.

How have you created your linked servers? What is the security like on them?

So you have a linked server to A from B,  to B from A and to B from C - Correct?

Regards
  David
0
TempDBACommented:
What is the exact error you are getting? It can be a double hop problem. And yup I second david's comment to make it simpler.
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
You have linked servers created in all servers, so they can connect to each other? And those linked servers are configured to allow RPC?
If you post the error message will help.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

LIFEEXPERTAuthor Commented:
dtodd:
My first thought is that htere is too much happening in one trigger firing.

That is, calling a stored procedure on another server is holding an implicit transaction too long, so this is likely to not scale well.
This was my first thought as well until I copied the tables to the server.

How have you created your linked servers?
What is the security like on them?

So you have a linked server to A from B,  to B from A and to B from C - Correct?

   Please explain.. not sure what you are looking for:
    Server A.. has RPC, RPC OUT set to FALSE (I had changed this to TRUE, but it didn't make a difference so I changed it back to the way it was)
    Server B.. has RPC, RPC OUT set to TRUE
    Server C..I was in error... SERVER C is actually a different Database on SERVER B.

Security is set to SQL Server authentication and Windows Authentication Mode.


TempDBA..
Where would I find the error... none is being shown... it doesn't show anything.. I had tried trapping the error by running as stored proc and it generated something like...
The OLE DB provider "SQLCLI" for linked SERVER B does not contain the VIEW/TABLE name. The table either does not exists or the current user does not have permissions on that table.
I checked the permissions for SA and it looks a though they have rights to everything.
0
TempDBACommented:
So, sa has the sysadmin role on all the servers right. And your link servers are running using sa login?
0
LIFEEXPERTAuthor Commented:
TempDBA: Yes to both of your questions
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
Can you post the sp code? At least the T-SQL command that are trying to access the linked server?
0
LIFEEXPERTAuthor Commented:
EXEC SERVERB.DATABASE.DBO.PROCNAME, @ID_1, @NAME
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
I meant the code inside the sp, not the code for calling the sp.
0
LIFEEXPERTAuthor Commented:
This is the portion that if remarked out it works fine...if not it fails

UPDATE T1            
    SET      A= RTRIM(T5.DDD) + '@HAPPY.NET' ,
      B= RTRIM(T2.NAME) ,
      C= (SELECT RTRIM(NAME) + '@HAPPY.NET' FROM SERVERB.DATABASE.DBO.PEOPLE WHERE (ID = T5.SSS)) ,
      D= (SELECT RTRIM(LNAME) + ', ' + RTRIM(FNAME) FROM SERVERB.DATABASE.DBO.PEOPLE WHERE (ID = T5.SSS)),
      E= T5.AAA,
      F= 1
FROM EMAIL_TABLE T1
LEFT OUTER JOIN SERVERA.DATABASE.DBO.ABC AS T2 ON T1.ID = T2.ID
LEFT OUTER JOIN SERVERB.DATABASE.DBO.DEF AS T5 ON T2.ID = T5.ID
WHERE T1.ID= @ID1

I also was able to determine that the if I remarked out :
LEFT OUTER JOIN SERVERA.DATABASE.DBO.ABC AS T2 ON T1.ID = T2.ID
and replaced it with a  local table on SERVERB it would work...
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
There is an issue with query linked server tables/views:
The base table or view should be created with QUOTED_IDENTIFIER and ANSI_NULLS set to ON.
Can you check that?
0
LIFEEXPERTAuthor Commented:
They are both set to ON
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
Can you change your query and use OPENQUERY instead of direct reference?
Example:
SELECT * FROM OPENQUERY(ServerB, 'SELECT * FROM Database.dbo.People')
0
LIFEEXPERTAuthor Commented:
Are you suggesting...create a table variable for that table. Use your query to insert into it... then join that to the update query?
0
LIFEEXPERTAuthor Commented:
Please keep in mind that if I run this from SERVER B. It has no problems executing as originally written. However, I did tried the OPENQUERY and work also if run from SERVER B.

SERVER A is still the not executing.

It's as if the Trigger won't allow an update to a table that isn't on its own server.
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
I tried to find information about issues between triggers and linked servers but didn't find nothing relevant.
Have you thought about replicating data between databases instead of updating with trigger?
0
LIFEEXPERTAuthor Commented:
I had to come up with a make shift solution. I had all the data gathered and prepared on SERVER A then had the trigger insert it into the table on to SERVER B. Don't know why but this works.
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
Vitor MontalvãoMSSQL Senior EngineerCommented:
Unfortunaly I couldn't get it :(
Only found an issue with deleted and inserted tables, but seems like you aren't use them.
A least you resolved your problem.

Cheers
0
LIFEEXPERTAuthor Commented:
initial problem was not resolved, but found and alternative
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.