Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 multicompany on one single database

Author  Topic 

AskSQLTeam
Ask SQLTeam Question

0 Posts

Posted - 2006-11-13 : 07:57:10
MK writes "hi,

I need to create a database for holding company, having common tables (like client ,agency, product tables) to be shared by all subsidaries so that all users in the holding can access them, and other tables (transactional ones) to be accessed by the users of each subsidary.
which is the better way to choose: create single db for all subsidaries or createing a db for the common tables and another db for transactional ones?


Regards,"

harsh_athalye
Master Smack Fu Yak Hacker

5581 Posts

Posted - 2006-11-13 : 08:26:43
Why create two dbs? It's just a matter of giving appropriate access to the users. Give access to common tables to all users while for transaction tables give access to respective subsidiary users only.

Harsh Athalye
India.
"Nothing is Impossible"
Go to Top of Page

derrickleggett
Pointy Haired Yak DBA

4184 Posts

Posted - 2006-11-13 : 12:27:23
I would generally create one database. There are always exceptions possible; however cross-database joins can be harder to enforce from a security and data integrity perspective. It shouldn't be that hard to build the appropriate security into both the database and application. This is a fairly common scenario.

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2006-11-13 : 12:52:14
More of a pain to restore multiple databases "if the worst happens" too.

Kristen
Go to Top of Page

derrickleggett
Pointy Haired Yak DBA

4184 Posts

Posted - 2006-11-13 : 14:14:38
Well....we don't plan on ever having a disaster, so that's not a considation.



MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2006-11-13 : 15:20:30
Well ... it won't be a consideration if you are not planning for it, will it? ... until it happens!

Kristen
Go to Top of Page

derrickleggett
Pointy Haired Yak DBA

4184 Posts

Posted - 2006-11-13 : 18:41:59
You know better than that Kristen. Of course, we're planning. I am at a new company though. It's always fun when you walk in the door.

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2006-11-14 : 00:40:16
Yeah, but you know what you are doing, so you would know about restoring to Point-in-time for multiple synchronised databases.

Folk who weren't aware of that would presumably just "restore last full backup for each database" - and then have inconsistent data for the several minutes it had taken took for all the backups to be generated.

Kristen
Go to Top of Page
   

- Advertisement -