Hi @pontus.berglund ,

As far as I know this it not possible. 

Hi @bas.hopstaken,

I was assuming that could be the case.

@Christian Hauggaard, should I make a post about this in the ideas section, or could you move this post there? Let me know what you think is best.

If you are using a single SQL instance to host all databases you could consider adding views in one database that combines all together. Are you wanting to combine them because they are the same structure split across different databases? Then you do the combination after the ODX in your DWH instance. That is what mapping sets are for.

If the structures of the databases are different, then I would wonder why you would want to treat them as one entity.

Hi @pontus.berglund,

Can you clarify why you would want to use multiple databases within the same connection?

Thanks,

//Alex

Hi @rory.smith and @AvanWijnen,

We do indeed have a SQL Server data source with around 10 databases with the same structure, tables, views etc. I think it would be “cleaner” to have the same data source for all of these. Now we have 10 similar data sources, which was albeit not much work to create thanks to the copy function in the portal.
As you suggested we will map the common tables together in the DW instance.

Thanks!

That's exactly what the copy function is for @pontus.berglund .
I also want to highlight the possibility to map multiple tables at once (see video).