Hi again, the system I am developing is a little "unusual". What I mean with that is that there isn't just one database I connect to, but several. By "several: I mean potentially hundreds. Let's say that my company's database is called OracleA and there are other vendors, whose database has a completely different schema. Let's call these MSSQL_X and MSSQL_Y (they don't have the same schema either). In an installation of our system we might have to connect to 10 OracleA DBs, 25 MSSQL_X and 10 MSSQL_Y.

Given this scenario, I'd generate 3 LLBLGen assemblies. What is the best way to use these assemblies in a multi-threaded/multi connection situation?

For instance, DbUtils.ActualConnectionString lets me specify the connection string to one of the 10 instances of OracleA. How do I change that while multiple threads can potentially try to access different instances of OracleA?

Specifically, thread 1 might need to connect to OracleA@PC1, thread 2 to OracleA@PC2, thread 3 to MSSQL_X@PC3 and so on. I obviously cannot serielize the requests of the first 2 threads, but if DbUtils is the kind of singleton I take it to be, there doesn't seem to be an alternative...

Bear with me if the question is silly, but I need to know the implications of working in a multithreaded/multiconnection scenario like this.

Best regards, Alessandro

Hi Alessandro.

Actually the answer is easy: for that scenario the best approach is go on the Adapter TemplateSet.

No way to do this with SelfServicing? I prefer that model as it is a bit more intuitive...

kingalef wrote:

No way to do this with SelfServicing? I prefer that model as it is a bit more intuitive...

Hey Alef, small world, isn't it? I'd suggest you to take the adapter path as well.

Sure is a small world Miha I thought you said you didn't use LLBLGen

kingalef wrote:

Sure is a small world Miha I thought you said you didn't use LLBLGen

On the contrary. I use it all the time.

Great to know.