July 7, 2013 at 11:25 am
Comments posted to this topic are about the item Your Frame of Reference
July 8, 2013 at 3:01 am
I agree we have to view the problem from the clients perspective. Its a skill I pride myself on.
Can I just whinge about the link to the updateable snapshot?
What's wrong with updating the base table and then regenerating the snapshot? This is a far better solution than updating the base table and reading some data from the snapshot and some from the original database as proposed in the article. :sick: The approach discussed in the article leads to data inconsistencies.
IMHO
July 8, 2013 at 7:14 am
[font="Verdana"]
Nice Article with very good title.
My frame of reference and general work environments do not let me to try to invigilate new technologies and even to implement solutions other than practiced in my past. We may need to hear the debate such as "reinventing the wheel" in very broader sense, or at least credit from our managers.
But surely the new enhancements in development tools should be given a chance to clearly help ease our new developments or upgrades.
Thank you!
[/font]
July 8, 2013 at 10:32 am
Jamie Ingram-729524 (7/8/2013)
Can I just whinge about the link to the updateable snapshot?What's wrong with updating the base table and then regenerating the snapshot? This is a far better solution than updating the base table and reading some data from the snapshot and some from the original database as proposed in the article. :sick: The approach discussed in the article leads to data inconsistencies.
IMHO
I'm not sure if this is an issue with data inconsistency. I believe the scenario was that someone needs to work with data at a point in time for reconciliation. Using some app, rather than rewriting the app to also point to the existing database while reading from the snapshot. With this technique, you can update some information in the existing database, and if you are reading from the same view/synonym, you see the updated data.
July 9, 2013 at 7:04 am
Somewhat related... Oracle has a feature called "Flashback" that leverages the transaction log to query the state of data for any table at a point in time using the "AS OF TIMESTAMP" clause of the SELECT statement. I can see how this could come in handy for quickly viewing past modifications when change data capture isn't implemented, or even recoving data without going to backup.
SELECT * FROM employees
AS OF TIMESTAMP (SYSTIMESTAMP - INTERVAL '60' MINUTE);
What do you think?
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply