# tables in SQL

Results 1 to 2 of 2

Thread: # tables in SQL

  1. #1
    Rob Guest

    Default # tables in SQL

    I have an application that is going to be implemented for<BR>several orgs. It will all have to run off one SQL Server 7 database.<BR>I do not want to mix data across orgs in each table so I want to make a seperate set of tables for each org. Will I pay a performance penalty for having this many tables? Will this<BR>rapidly increase the size of my SQL database?<BR><BR>Thanks.

  2. #2
    Join Date
    Dec 1969

    Default RE: # tables in SQL

    You may consider creating separate databases for each org. There should be no performance hit and the database shouldn&#039t grow any larger than it would if you had all the data in the same table.

Posting Permissions

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