Designing a Database to Contain data for Multiple Clients/Companies

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » SQL Server 2005 Security » Designing a Database to Contain data for...

Designing a Database to Contain data for Multiple Clients/Companies

Rate Topic

Display Mode

Topic Options

Author

Message

dinovotpa

Posted Wednesday, May 20, 2009 8:29 AM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, September 02, 2010 2:28 PM
Points: 5, Visits: 90

The company where I am working is growing. We are bringing on more Clients and someone suggested that we'll need more databases (maybe 1 for each. client) - yea my heart stopped for a sec. Not a great idea if you have thousands of clients huh? yea not gonna take that approach.

Well I know there has to be someone out there who has encountered this situation.
Where I used to work someone put a CompanyID column in ea. table to segragate the data by Company.

If anyone has information of different approaches. Pros/Cons etc it would be greatly appreciated.

Thanks,
Mark.

Post #720598

Pradyothana Shastry

Posted Wednesday, May 20, 2009 10:56 AM

SSCommitted

Group: General Forum Members
Last Login: Monday, March 25, 2013 5:30 AM
Points: 1,640, Visits: 423

Do you mean to say each database for indivisual client on the same instance???

- Pradyothana

http://www.msqlserver.com

Post #720759

dinovotpa

Posted Wednesday, May 20, 2009 12:55 PM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, September 02, 2010 2:28 PM
Points: 5, Visits: 90

Yes. My manager though is having none of it - thank God!!

I guess this person has done some programming in the past - those are the folks that scare me.

They seem to know just enough to be dangerous and also have a mgrs ear. Thankfully my mgr
also still codes so she's not out of touch.

Post #720827

« Prev Topic | Next Topic »

Permissions