Linked Server in SQL 2005 Query Problem???

I have the following query in M/S SQL Server 2005 Express which runs against a Linked MySQL Server.  Nothing fancy just a select query that joins the product order details table with the work order table.  

select* from openquery(linked_mysql, 'SELECT PRODUCT_ORDER_DETAILS.PRODUCTID, PRODUCT_ORDER_DETAILS.UNITPRICE, PRODUCT_ORDER_DETAILS.QUANTITY, WORK_ORDERS.* FROM WORK_ORDERS INNER JOIN PRODUCT_ORDER_DETAILS ON WORK_ORDERS.WO_ID = PRODUCT_ORDER_DETAILS.WO_ID')


I get the following error when it executes ...

Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command.  The results, if any, should be discarded.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command.  The results, if any, should be discard

Any help will be appreciated.

ET
LVL 19
Eric ShermanAccountant/DeveloperAsked:
Who is Participating?
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
I see 2 potential issues:

the WORK_ORDERS.* could have a column name which is the same as for those for PRODUCT_ORDER_DETAILS that you name explicitly. don't use * here, but specify the columns explicitely, and make sure there are no duplicate column names returned.

there might be columns having data types that are not "understood" correctly by the linked server provider...
in which case, you might try to change the provider, or make sure the data types returned are "understood".
from oracle, I remember the following data types being a problem: BLOB, CLOB, etc, TIMESTAMP, NUMBER without size specification ...

in MySQL, it could be BLOB ...
what data types have your columns in the 2 tables ?

0
 
EvilPostItCommented:
Try doing a direct select. When you have a linked server you dont need to use openquery.

SELECT * FROM LinkedServer.Database.Schema.Table

Open in new window


Do this error?
0
 
Eric ShermanAccountant/DeveloperAuthor Commented:
EvilPostIt ....

I tried this ....

SELECT * FROM linked_mysql.localhost.MyServerName.product_order_details

and got this error ...

Msg 7312, Level 16, State 1, Line 1
Invalid use of schema or catalog for OLE DB provider "MSDASQL" for linked server "linked_mysql". A four-part name was supplied, but the provider does not expose the necessary interfaces to use a catalog or schema.

ET

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.

 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
>A four-part name was supplied, but the provider does not expose the necessary interfaces to use a catalog or schema.
as the error indicates, you cannot use the 4-dot-naming with MySQL providers so far.
0
 
Eric ShermanAccountant/DeveloperAuthor Commented:
angelIII

The only field that would be the same between the two tables is the WO_ID but I'm not selecting it from the product_order_details tbl.

I will try your suggestion and select the individual fields from Work_Orders rather than the * to see if this makes a difference.

ET
0
 
EvilPostItCommented:
Sorry havnt played with MySQL providers. I will let you 2 get on with it. :-)
0
 
Eric ShermanAccountant/DeveloperAuthor Commented:
>>>>as the error indicates, you cannot use the 4-dot-naming with MySQL providers so far.<<<<<<

Well, that makes sense ....  just a question on this method though ....

Using the 4-dot-naming and say if I was trying to connect to a remote server  something like 11.111.111.11

How would you specify the remote server address (replacing the localhost) using the 4-dot-naming as shown below???  

SELECT * FROM linked_mysql.localhost.MyServerName.product_order_details


Thanks,

ET
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
you can leave, with some providers, the part empty of what is not needed.
as the "linked_mysql" already specified to which server you connect, you don't need the info (ip address) at all any longer
0
 
Eric ShermanAccountant/DeveloperAuthor Commented:
Ok, that makes sense also ...

Regarding my original question ....  When I specify the individual fields seems like the error is generated when I included fields of "LongText" from MySQL.

Any ideas on how to get around this as those are comment fields which will need to be included in the query.

Thanks,

ET
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
LongText sounds like "blob" ... can you cast that or use LEFT() function to get a shorter string?
0
 
Eric ShermanAccountant/DeveloperAuthor Commented:
Yes, that can be done.  I used this work around to accomplish what you suggested.

In the MySQL ODBC Data Source there is an option to "Limit column size to signed 32-bit range".

This worked and all seems to be ok.

Thanks for all your help.

ET
0
 
Eric ShermanAccountant/DeveloperAuthor Commented:
Thanks and you were correct on the blob or longtext fields.

Seems like the M/S Provider is unable to handle data types longer than 32bit.

ET
0
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.

All Courses

From novice to tech pro — start learning today.