Creating tables dynamically in Appian, firing SQL Queries and Maintaining sessions

1) Yes

2) Yes

3) No

I would not do any of it, but I am interested in your use case. Would you mind telling us what you intent to do?

Thanks Stefan,

My use case is like follows for the first point:-

1. A user comes up in the portal, I want to store some data of that person in the Appian db's dynamically created table specific to that use data only (the data will be populated from third party api). Now, remember, my third point, I want to flush out that table if user logs off or session is closed. 

So now could u pls tell me how I can do this ?

Thanks Stefan,

My use case is like follows for the first point:-

1. A user comes up in the portal, I want to store some data of that person in the Appian db's dynamically created table specific to that use data only (the data will be populated from third party api). Now, remember, my third point, I want to flush out that table if user logs off or session is closed. 

So now could u pls tell me how I can do this ?

Your use case is not supported in that direct way. Can you add a few more details?

Is this about Appian Portals? I mean, with an anonymous user? What ist the use case?

Users are not anonymous. We will add the appian users to the portal.

what do you mean by this?
I am not sure if terms are 100% clear.
portals should be used for external, e.g. unkown users to start an application, a request, to add documents or whatever.
-> if you want to have an interaction with an registered known, let's say, company internal user, you don't use portals. You use a site or tempo. 

In Appian, "Portal" means a separate small user interface specifically made to interact with anonymous users.

When you explain your use case in more detail, I will try to support you further.