We have Several companies on one application server and all the databases reside in one large database on Sql Server. We would like to break out the different companies into different databases on the same instance of Sql Server. Does anyone have instructions on doing this?

As I know, it is not possible to put different tables in different databases in same instance.

I think the restriction is because each user can only link to one db group. The db group is actually the database name in the instance.

We have a customer facing the same situaion. They want to separate each baan companies in different database. The outcome is now they have several instances of SQL Server running together.

Tritonbaan is correct I looked at this a few years ago. The only idea I came up with was to use NDF files. It allows you seperate out your tables in to different files so you have mdf and ndf files. you can put the ndf files on different disks to improve speed it is also possible to backup and restore ndf files independantly. I was looking at it to put my archive company into a different NDF file so my production backup would be quicker as the archive company only changed once a year.

So why could you not just create multiple logins for users that need to access more than one company? Am i understanding that you can do this but the user can not log into another company?

To create different users to access different companies is not a workable solution. The problem is because every user need to access company 000.