best to handle big Company and multi database...

[Robert Iliuta]

Hallo,


I need your advise regarding one big project I have to do .
It's a company which has 6 division and each division has around 200 sub division.
They want at least once per quarter to synchronize all sites. (6x200)
Every sub division site will not have more then 1000 records. They will grow but very slow. There are some sub divisions with 20 records.

Now what is the best approach?
1.) to make folders and get separate data base for each sub division? (when they login redirect to data base)
2.) to make one data base and filter by sub division? (one big data base filtered by user/sub division)
3.) ? other possibilities?

I need the application to handle hundreds of user online at the same time. They could be around 200 users online at the same time.

What would be the best option? advantages? speed, stability, easy to administrate, etc
Can I work with TPS? if SQL is the best what SQL to choose? (preferable free)

I have to do couple transactions and I will use LOGOUT...this will help If I get separate data base? (option 1)

Ok, if someone has similar application and like to share some experiences I appreciate a lot!
Also if you have more advice or anything regarding this subject is welcome!

If you need more information please let me know.

Thank you,
Robert
 

[peterH]

Hi Robert,
I'd definately go for option 2. You avoid the hazzle of creating - and maintaining - 1200 data bases! The amount of data that you mention and the setup in general does not justify that either.

Whether you go for tps or sql doesn't really matter but personally I'd choose sql.

Peter

[Bruce]

I'd make a big database in this case.
yes I'd use SQL.
And I'd also use random-generated-strings for uninque ID's - not auto-number.

cheers
Bruce

[Robert Iliuta]

Thanks Peter and Bruce.
I will test both TPS and SQL.
Regards,
Robert