It may look a little ugly but until there is a proper intraweb manual, I would place all database components, database connection too, in the same form along with visual components, squeezed in the corner so that they not take up room. I prefer safety to appearance and SQL queries are independent of each other so no need to use UserSession. As we have seen, everything put in the form class is safe, so this is a sensible conclusion. Non-visual components code placed in the visual form are automatically put by intraweb at back-end. Anyway, most books about database have advised that as it is simple. If the form just reads user query, it is all right to put the query string variable in the UserSession, so another form with database components will read the query and execute it. In my country, Poland, the most commonly used database is firebird, which is also free for commercial use.
Some invisible components, especially including intraweb, have to be, after all, put on the visual form, like timer, video etc., and so I would not worry but put database components on the visual form in one place overlapping so they take up very little space. Also I do not see why database connection component should be put in the UserSession. Database connection component can have many copies for each visual form. To access database components properties you have a window in top left Delphi corner where form components are listed.
Some invisible components, especially including intraweb, have to be, after all, put on the visual form, like timer, video etc., and so I would not worry but put database components on the visual form in one place overlapping so they take up very little space. Also I do not see why database connection component should be put in the UserSession. Database connection component can have many copies for each visual form. To access database components properties you have a window in top left Delphi corner where form components are listed.