The main reasons that I could think about keeping them together is so that you only have to maintain one schema and for manageability. However there are tools now that are available for blasting changes to more than one location so schema maintenance is less of an issue.

It seems that you could keep the data together but you would have to be real sure that your application was only going to display the pertinent company information based on the company that was logged in. The risk should be minor with testing.

The other thing to consider is how much data would be in common and what amount of duplicate data you would be storing if you split this information up to company specific databases. That could get costly if there was a bunch of common data. My guess is that there wouldn't be based on your description.

No answers, but some things to consider anyway! :hehe: