Possible to join 20 dimension tables to a fact table, from the same SQL Server database?

[Niels2]

Hi!

I’m trying to visualize my data in QuickSight. However, after joining all my dimension tables to the fact table I get the following error: Your database generated a SQL exception…

Now I see that that if a dataset contains joins that the maximum capacity is 1GB.

So, I’m trying to join 20 dimension tables to my fact table but they are all from the same SQL Server database. Would that still be considered as a cross-source data set? And so has maximum capacity of 1GB?

Many thanks!

Kind regards,
Niels

[neelay]

@Niels2 What’s the SQL Exception?

[David_Wong]

Hi @Niels2,

Did you create a separate dataset for your fact and dimension tables? When you join datasets in SPICE, each one is considered as its own source even if the underlying database for each one is the same.

I believe you’re hitting the same limitation that was discussed in these 2 topics:

Join tables releases error, due to exceed join memory, need to increase size of join

Hello All, could some one help on this please, this is very weird, how come join limit only 1GB? now we can’t reduce of join, or else if we remove it will breaks whole dashboard, how to increase join size to 10 GB, please error: QuickSight ran out of join memory while processing your request. To join between data sources, the smaller source tables combined can’t exceed the join memory limit of (1GB). The largest one, “accounts_users”, doesn’t count toward the memory limit. To…

Joining dataset is not allowed due to capacity[High Priority]

Hello I am trying to join two dataset in spice, and i keep getting the issue mentioned in the picture. Can you please advice on what should be done? Please note that I tried to filter one of the datasets before joining and it is still not working. Thanks [imit]

[Sanjeeb2022]

Hi @Niels2 - The details provided by @David_Wong are really useful one. Also is it possible to use custom sql and then run it and bring the data to QuickSight for reporting. You can check the performance of the sql in any sql client tool before put it in QuickSight.

Regards - Sanjeeb

[Niels2]

Hi!

The error that I see is: ’ This can be caused by query timeouts, resource constraints, unexpected DDL alterations before or during a query, and other database errors/ Check your database settings and your query, and try again. ’

[neelay]

@Niels2

You can find the SQL limitation below.

Data source quotas - Amazon QuickSight

But most probably your request is being terminated by your engine.