I paid for an enterprise license and then found out I can't do this.
my use case is for some ad hoc etl type use- query from one db on one server, then do insdert to a different table(s) on a different server (or even to a local sqlite file).

Pretty disappointed this isn't possible currently.

@Jozef That's cross server support. I'm mainly concerned about multiple databases on the same server.

Our data are on a lot of different databases (mainly ORACLE MYSQL and SQLSERVER).
Cross database support would be THE BIG STEP FORWARD.

@Joe

Cross-Database (same server) should be enabled by default (or by user settings when setting up the connection)

Cross-Server would be ok, to only to be enabled if LinkedServers are setup by the DBA...

I would love this feature too. In a system I have to work with the data is splitted in four databases (on same server) and I often need data from two databases (raw data from communication backend plus additional meta-data).

This is my top request for LinqPad. It's great, but limited in this area. Crippled, really. SQL can do it, but LinqPad cannot, which is very disappointing.

I thought this would be simple. I just want to use two DB's in a query.

So hard needed!!!

@Joe Multiple servers isn't nearly as important as multiple databases on the same server. It's impossible to write migration scripts from one db to another on the same server for example.

Querying across multiple servers is possible in SQL only if the DBA first sets up linked servers. Because LINQ translates to SQL, this same limitation would hold. Do you think this would this limit its usefulness?

The workaround will not work when multiple database Servers are involved. We need multi-connection support.

This is basically a must-have feature for me to find linqpad useful. Please consider this for the next version!

Agreed.