for others also researching this issue. you will come across an alternative notation like this: select * from LINKEDSERVER.DSNNAME..TABLENAME.
this seemed to work, but wound up throwing an access denied error from my remote server. not sure why as i can use the dsn from within a dts package without incident. i was not able to diagnose that and turned on the level zero switch and it works now. thank you!!
Thanks,
man, you save me… thank a lot.-
Thank you! This solved my problem completely!
This tip was helpful especially with having the linked server to work with a Excel spreadsheet through a ODBC DSN (MSDASQL).
Thanks!
Tnanks a lot.. you really help me with my problem.. !!
for others also researching this issue. you will come across an alternative notation like this: select * from LINKEDSERVER.DSNNAME..TABLENAME.
this seemed to work, but wound up throwing an access denied error from my remote server. not sure why as i can use the dsn from within a dts package without incident. i was not able to diagnose that and turned on the level zero switch and it works now. thank you!!
Thanks. It works in our shop.
Thanks for the tip. This saved me a lot of time.
Worked for me. Thanks for the tip. But I wonder.
I could change “level zero” back to 0 (off) and it would still work while on the server. Could it just be initializing MSDASQL on the server?
Testing from my PC, it didn’t work set to 0 from the client, but changing “level zero” again back to 1 fixed that problem as well.
I’m not sure John. I have very little actual understanding of the problem despite trying to decipher books online.
Thank you guys . It works great.
Thanks a lot. I was looking for this.
The Google Gods are smiling on you. Thank You very much. The feature also works
on ProvideX databases. We thank you.
Thank you for your post. It saved me a lot of time.