Home Forums SQL Server 2012 SQL Server 2012 - T-SQL Best way to move data from one db to another and maintain relationships ? RE: Best way to move data from one db to another and maintain relationships ?

  • DiverKas (6/20/2013)


    William Plourde (6/20/2013)


    So a person could move from db A, to B to C to D etc?

    Yep, that is correct. Assuming 6 dbs out in the future. A person (and all their related data) can move from any db to any other db. Possibly more than once over time due to business logic.

    Just curious, why different DB's? Why not partition the tables instead and save the headache?

    There are some business and potentially legal reasons behind the decision. I have not personally used partitioning but I know what it is and I'll brush up on the topic to see if it can help. But to make a long story short if our system gets large enough we can dynamically add a new database and auto-magically start loading data onto it,even if that db is on another physical server. So it's not quite the same as partitioning. Its more like home grown load balancing for data.