Joins on linked servers using functions

v2.5.14

Querying joining a linked server table to a local server table using a function causes it to hang for about 15-20 seconds. Example.

Select *
From dbo.Names n INNER JOIN LinkedServer.Database.dbo.OtherTable ot ON n.ID = Convert(int,

Typing after this point causes this error after just about every keystroke:

---------------------------
SQL Assistant - Error
---------------------------
Exception: CheckKey(44,3342337)
---------------------------
OK
---------------------------

SQL Assistant doesn't currently support linked servers. We are trying to stay away from linked servers because of so many known problems with them. If you are coding distributed queries involving linked server tables or views pointing to linked tables, please use the Suspend menu in SQL Assistant to suspend it temporarily. You can resume SQL Assistant after you are done with such query.

I'd rather it be able to detect that it is referencing a linked server and simply not display a popup, than to freeze the window. BTW, Query Analyzer frees up a lot faster than Management Studio.

Query Analyzer uses ODBC, while Management Studio uses SMO. Not that it matters for SQL Assistant, but the internal working of these protocols is different, that's why you see some differences in response times.

Not sure if this is going to help, but you can try customizing database catalog queries in SQL Assistant options (start with "Objects" query) and adding some filters to the WHERE clause excluding anything that starts with your linked server name.

I know it's a pretty old topic - but is there a way to query the linked server, if I know that I surely want to?

No. We are not planning on supporting Linked Servers because Linked Servers is very unstable future by design. If a linked server connection is not configured correctly or a bad driver is used, it can easily crash the server, which happens quote often. We don't want to deal with complains that SQL Assistant crashed production server or even waste time investigating such reports.

Besides, you can always create a local view pointing to remote server and using OPENQUERY or similar method. SQL Assistant can be then used to query the local view.