|
-
 Originally Posted by divroro12
PavB, what about materialized views or Transportable tablespaces?
Any thoughts on those?
Materialized Views have to be created over a dblink - in this scenario - which I think defeats the purpose - I have to agree that it looks like a very atractive and elegant solution.
In regards to Transportable Tablespaces, I think you can generate a Transportable Tablespace only on Enterprise Edition while it can be imported into any edition; plaforms with different endian format would require some extra setup synchronization like compatibility_level I think. If laptops are not running Enterprise Edition it wouldn't be possible to send data to the central database this way. Also, source and target database have to have the same character set and national character set configuration. I have the feeling this solution keeps adding potential issues to the solution.
Last edited by PAVB; 01-26-2012 at 04:18 PM.
Reason: typo
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|
Reply With Quote