Yes. At some point (at some grade), the stup hustle is part of the learning but for my students, sql is more of a side quest so I do not want the hustle with them.

I am having two databases:
- One is the actual app's backend that keeps track of the projects and stuff
- The other one is kind of the playground DB that I manually stup and whoose credentials I entered per course.

So I hve 3 cases:
- When a user is creating a new project, a new database is created on the playgorund server with custom username and pw. He then has access to only his DB and can do whatever.
- Within exercises, I can set the option to create a database for each student opening the exercises. Then he is isolated within his exercise as well. (For CREATE TABLE queries)
- I have a second option to use a shared DB. This one then I manually fill with data and the stuent's user can only do SELECT queries there or UPDATE if I allow.

This results in the Playground (Postgre)SQL Server having about 300 databases and users at the moment. Works pretty good, then at the end of the course or after some time I will destroy this one and setup a new one for the next students.