pls suggest methodology for building select query when there are many tables to choose from

  • Would a developer kindly provide advice...

    I know exactly what my results set should look like. It comprises of 30 columns found in 100+ tables and views in a database containing 3 schemas. I am to find the most efficient query for getting those.

    1. With so many tables how does a developer get a handle of which tables and views make the most sense to use, for example, utilize the shortest path between parent/child relationships over FK/PK paths? What methods and tools does a developer use to make that task seemingly easy?

  • When I've had to reverse-engineer systems with a large number of tables in past, it really helped to examine the existing system to see how they pulled data.

    In reality, my general advice is very simple:

    Generate or retrieve a db schema diagram

    Start simple

    Add complexity one step at a time

    examine performance with each additional step of complexity

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply