My client has a complex web analytical app that guides the user through a series of screens to determine the what they want to see. The app is designed to create a new SQL Server table for each user session populated with the content specific to the user's declared needs.

There is a common schema for all of the SQL Server tables - they differ only in their data content.

The developers wanted to create 10 or 12 identical copies of the same Tableau viz, each connected to a distinct specific tableau and then round-robin these viz-table pairs among the users. It wasn't hard to convince them that this isn't a good solution.

Now they want to be able to have a single Tableau viz that can be wired to dynamically access user-specific SQL Server tables at run time. I'm not sure whether or not this can be done. It doesn't feel like it, at least feels like it's outside Tableau's intentional design parameters.

But it's not an area I'm comfortable in having a definitive opinion in, so can anybody shed some light on things?

CAN it be done? If so, how? (this would be terrific)

Can it be confirmed that it cannot be done? Also good, but harder to be definitive with.

I have urged them to consider using a single table so that they can pass filter parameters to Tableau server identifying the user, which should work, but they've dug in their heels at that. Their claimed concern is that the processing load of adding the user-specific rows to the table will be too great.