Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Sounds like you need to do some serious data-modeling. </p> <p>You definitely need it for the long term so that you don't get yourself into serious strife. (if there's one thing that will have a significant impact on your ability to support / extend systems and support business growth - it's data management). The good thing about (business) data is that your business stakeholders will (or should) have a good understanding of it and be suitably motivated to support you. The value such an exercise will bring should be an easy sell. Having some of this in place in the short term will help as well. </p> <p>Data sources which come with packages products (Commercial Off The Shelf - COTS) will not be open to change without putting those systems at risk - but that doesn't mean you can't use ETL and other databases to create data marts that bring disparate data together. In this sort of an approach the data modeling, and data mapping between systems will be important - but also the timing.</p> <p>You will have more flexibility with in-house apps - but you might want to resist tactical changes unless you have a very compelling reason, otherwise you'll probably have to re-work them anyway.</p> <p>As part of this exercise you'll want to consider the <a href="http://en.wikipedia.org/wiki/System_of_record" rel="nofollow">System of Record</a> of each piece of data - where does it come from? Who owns it? You can start at a high-level by drawing up a conceptual data model, this will probably deal more with logical datasets than specific "columns".</p> <p>Use this information to guide further decisions.</p> <p>In terms of your immediate approach (and your question): in general terms it'd think about putting a layer of abstraction between your systems and the data, so that the applications are cushioned from change when that happens.</p> <blockquote> <blockquote> <p>Create a new EF data model, responsible for providing information that only the application needs, while duplicating some common entities such as the Employee.</p> </blockquote> </blockquote> <p>The big issue with duplication is getting the data into a state thats muddy - which is the "real" record. This can easily kill you. What are the benefits of this approach in your context? Would you be doing this from a supportability perspective? Ease of development?</p>
    singulars
    1. This table or related slice is empty.
    1. POBest approach to Architect the integration of two separate databases?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAdrian K
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHello Adrian, Thanks for your response. The problem we're facing is that we have two aspects of our business running on different databases.. Each Aspect has a wide variety of applications that we can't afford to re-write. We're looking for a way to integrate the two databases without starting from the ground up, for future projects, using Entity Framework 4 and C#
      singulars
      1. PO
      1. USZack
    2. COSo I guess mapping out the data flows and data mapping would help you manage that integration. I'm guessing you want to integrate the "data" - not the actual physical databases; its a subtle difference that people don't always see.
      singulars
      1. PO
      1. USAdrian K
    3. COAh yes, that's correct. We're unable to redesign the databases as they have too many applications using each one, modifying/re-writing them isn't an option. - An approach to Integrating the data is what we're after.
      singulars
      1. PO
      1. USZack
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload