I'm working on a project where we have many companies as customers.
At the moment we have one database for all companies, but we are consider to use one database for each company instead.
At the same time we want to use the same release (the same assemblies) to all companies. And then decide connection string depending on what company it is.

How would this work with NHibernate? Would we have to have one SessionFactory for each company?

/Carl

If you launch a separate application instance for each company, then you only need one session factory for that company's database in the application. You can pass the connection string and other properties manually to the Configuration object.

Forgot to say that it is a web application. Is it possible to launch separate instances of a web application without having multiple copies of the assemblies?

I should also say that its a ASP.NET 2.0 project.

No. If the schema is the same for each database then you can still use a single session factory. When you ask the session factory for a session you can pass in the connection string of the db that you want it to talk to.

BOb

Thanks Bob! Didn't know of that.

But couldn't there be trouble with caching when doing this? Like if some object in one of the companies databases has the same ID as an object in another companies database.

Only if you are using a second level cache.

BOb

Thanks again Bob!