Advice: Ad/Dis vantages of mulitple Back end Databases

[Ktx7ca]

Hello

I'm wondering what the advantages and disadvantages of having more then one back end database

thanks for the advice

chris

 

[JoeAtWork]

The only reason I ever have for different back end databases is if the information is already in different places. If I'm starting from scratch, then I'm going to use the same back end database unless there's some good reason not to.

Advantages to one backend:
1. Only one connection kept open
2. Relationships and other schema information is in one system
3. Maintenance cost lower - only need to worry about one connection

I don't see any "advantages" to having multiple backends. It's a solution for certain problems, usually when you need to gather data from disparate places.

 

[TheAceMan1]

How are ya Ktx7ca . . .

[blue]I'm wondering what the advantages and disadvantages of having more then one back end database[/blue]

This is academic to me as far as pro's and con's are concerned ... [blue]you need the tables you need [/blue], so you can finalize your design! Its easy enough to get to completion and then take into account performance issues! ... [blue]No matter whats said ... you gota have the other backend.[/blue] Get there 1st and attack the performance isues when done.

[blue]Your Thoughts? . . .[/blue]

See Ya! . . . . . .

Be sure to see thread181-473997 [blue]Worthy Reading![/blue]
Also faq181-2886 [blue]Worthy Reading![/blue]

 

[ZmrAbdulla]

Another advantage(to overcome access' (dis)ability).
If you need to keep more than 2 gb data split into different database as Access can grow only upto 2 gb.

But at this stage everyone will suggest you to upgrade to some other database type like SQL server or MySQL

Zameer Abdulla