On 12/16/10 8:42 AM, Lars Marius Garshol wrote:
* Hugh Williams
What are the remote database(s) you are seeking to virtualize data into
Virtuoso from ?
To begin with we're looking at an ERP system known as IFS. However, there will
likely be 2-3 more systems in the first iteration. We envision separate
Virtuoso databases serving SDshare for each of these.
I'm aware that Virtuoso has support for replication etc that could probably be
used to do all this, but we don't want to turn this whole ecosystem into a
Virtuoso-only thing. We want the individual components to be loosely coupled to
one another, so that we can use what makes the most sense for each individual
component, rather that building something that's Virtuoso-only, and has to be
because that's the only thing the architecture will support.
I am sure you understand that as a fundamental principle, OpenLink
implements standards whenever such exist. If standards don't exist and a
problem persists, we innovate. If standards emerge later, we support
immediately.
The docs page you found below details whats happening at the lower level, but
the materialization of the views can also be performed using the Virtuoso
conductor with the following steps : [...]
Thank you! That seems like it could be a little easier when actually doing
this. I still found the lower-level approach useful for showing me what's going
on in technical terms.
Sure!
Whether this will work for us is not clear, I have to confess. For one thing
I'm not sure what the DBA will say when we explain that we want to inject
hundreds of new tables and triggers into their database. I'm not even sure we
can do it, since we can only look at views and not the real tables. And then
there's the performance etc.
Which is why you may opt for other approaches e.g. you replicate the
data from foreign source to Virtuoso instance, and build views atop
Virtuoso. Otherwise, you can use Transient Views atop ODBC / JDBC to the
remote DSNs.
If you want backward chained inference and change sensitivity then there
are no alternatives to what we've implemented.
But formalities aside this looks like it could be a good match for our
requirements.
Great to hear. Virtuoso was built from inception to deal with the vast
and timeless challenge of change-sensitive heterogeneous data access,
integration, and management :-)
Kingsley
--Lars M.
http://www.garshol.priv.no/tmphoto/
http://www.garshol.priv.no/blog/
------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
Virtuoso-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/virtuoso-users
--
Regards,
Kingsley Idehen
President& CEO
OpenLink Software
Web: http://www.openlinksw.com
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen
