One Database VS Many Databases

Results 1 to 2 of 2

Thread: One Database VS Many Databases

  1. #1
    Join Date
    Dec 1969

    Default One Database VS Many Databases

    Hi,<BR><BR>I have an Access database which holds quite a bit of data over various tables. Some of these tables relate to each other. The thing is one of the tables constantly needs backing up and updating on another system we have, where the large table doesn&#039;t really need to backed up that often. Is it better to seperate this table in to another database, create a separate connection to it (DSNless in my ASP page) and query the other database using the SQL or leave it in the table, using the same connection and simpler SQL?<BR><BR>If i did this for the the tables I have I could have five databases, with the ASP page specifying five connections to five differenct databases.<BR><BR>Cheers<BR><BR>Carl

  2. #2
    Join Date
    Dec 1969

    Default RE: One Database VS Many Databases

    You could. But then, how are you going to do JOINs?<BR><BR>5 different connections sounds like a maintenance nightmare to me. Stick with the one database. That&#039;s my opinion.<BR><BR>Craig.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts