Una idea que espero te enfile en la dirección adecuada. Suerte


fox.wikis.com/wc.dll?Wiki~OutriggerTables~VFP
An OutriggerTable is what you get when you normalize a DimensionTable. You would then have a PrimaryKey in the OutriggerTable and a ForeignKey in the DimensionTable. The relation can be Identifying or non-identifying.

It is usually recomended to avoid using Outrigger tables if possible - since it affects query speed.

If the dimension tables are normalized into typical "snowflake" structures, as shown in Figure 2, two bad things happen. First, the data model becomes too complex to present to the user. Second, linking the elements among the various branches of the snowflake compromises browsing performance. Even when a long text string appears redundantly in the dimension table and can be moved to an "outrigger" table, you won't save enough disk space to justify moving it. The fact table is always overwhelmingly the largest table in a star join schema. In many cases, normalization can actually increase the storage requirements. If the cardinality of the repeated dimension data element is high (in other words, there are just a few duplications), the outrigger table may be nearly as big as the main dimension table. But we have introduced another key structure that is now repeated in both tables.
http://www.fortunecity.com/skyscraper/oracle/699/orahtml/dbm...
PortalSQL.COM Tu sitio sobre Sql-Server
... la idea no es usarlo como tabla temporal sino de tabla de respaldo o histórico,
para que queden reflejados como copia todos los insert que hagan en las tablas ...
www.configuracionesintegrales.com/miguele/ responder.asp?idforo=1&idPregunta=2022&pagina=0 - 11k - Resultado Suplementario - En caché - Páginas similares