Database Hosting

Hi all,

Our company is about to embark on rewriting our entire application to be truly client/server based, and bring the UI up to .NET. One of the additional services that our CEO wants to provide is the hosting of the software ourselves (to save our smaller clients the licensing costs of the database server software, etc).

However, the proposed solution to this is to simply have a single database with every client's data in it, and add a 'client-code'/'client-id' field to EVERY single table in the database.

Now, to me this seems to be a seriously flawed method of doing it, when a much simpler option (one database per client) is available.

What are your thoughts, and how do other companies provide a similar service?

Regards,
Murdoc

--