• I am not sure what your question is?

    Sorry Ron. I'll try to meke it clearer :blush:

    Thanks for the reply 🙂

    The data is separate by Location, ie the ContactID will unique to the Location as will be the SalesExecutive,Outcome etc

    Whilst using LocationID (and I left out a Location table on purpose as I did not want to constrain any design yet) will separate the Contacts by Location and by inference all it's associated data. I will need to retrieve all the SalesExecutive, Outcome etc for a specific Location irrespective of Contacts as a SalesExecutive may exists for a Location but not be referenced.

    The question is how to alter the design for performance and scalability.

    Three things occured to me

    1. A database per Location (140+ databases!!!)

    2. One database with tables repeated for each Location (partitioned views with 140+ tables!!!)

    3. Unique range of ID's per Location

    As I stated it is about performance and scalability.

    byw the Location of varchar(10) is fixed due to third party system, however the last 3 digits (1-999) is still in operation, but who knows for how long! it could change

    Far away is close at hand in the images of elsewhere.
    Anon.