By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,334 Members | 1,328 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,334 IT Pros & Developers. It's quick & easy.

DB2 Viper Testdrive

P: n/a
ZD-Net article:

http://news.zdnet.com/2100-9593_22-6057835.html
Download:
http://www.ibm.com/software/data/db2..._download.html
Docs:
http://publib.boulder.ibm.com/infoce...w/v9/index.jsp

Enjoy
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Apr 6 '06 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Just to give a brief idea, How XML in db2 is implemented as compared
to other Databases. XML in V9 DB2 is not stored as CLOB or BLOB
internally, nor shredded and stored as relational tables. XML is stored
as XML, rather as format which is in standards with w3c to enable
XQuery access to XML data. Which means that XML can be parsed by XQuery
Language (Like SQL For Relational data) and the XML file in one or more
pages in the table space, and the file is parsed only once to access
the data (because of architecture, when compared to be internal
implementation as LOBs).

What is in for App Developer is, once you store XML file in DB2 as XML
data type, you can use XQuery to access the data, can create
relational views out of XML data. Will not need complex transformations
that need to be done in application layer for manipulating the data,
most of XML manipulation can be done in Database layer.You can store
XML which adheres to some schema and hence do the checking using
database .

Another thing I feel, new for App Developer in Viper is the Label based
access control. You can define security policy for each object, even
attributes of the object (like columns in tables) and give access to
different roles.

Do check out Viper :) it has lots of autonomic features for
Administrators ..the who member management has gone for a an overhaul,
it faster, better and less maintanence.

Apr 6 '06 #2

P: n/a
Serge Rielau wrote:
ZD-Net article:

http://news.zdnet.com/2100-9593_22-6057835.html Download:
http://www.ibm.com/software/data/db2..._download.html Docs:
http://publib.boulder.ibm.com/infoce...w/v9/index.jsp

Enjoy Serge


Thanks for the interesting links on v9 ...

From reading the publib doc: Tutorial for native XML data store

"You can create tables with XML columns only in databases defined with the UTF-8 code set and a
compatible territory code."

But looking through the migration task(s), there is no mention of changing DB code sets.
What is the envisioned method to enable XML features into existing DB2 v8 sites?
Should a hybrid dual-DB configuration be employed, or better to first migrate v8 DBs to UTF-8 code set?
Eric

Apr 6 '06 #3

P: n/a
Eric.Jones wrote:
Serge Rielau wrote:
ZD-Net article:

http://news.zdnet.com/2100-9593_22-6057835.html Download:
http://www.ibm.com/software/data/db2..._download.html
Docs: http://publib.boulder.ibm.com/infoce...w/v9/index.jsp

Enjoy Serge


Thanks for the interesting links on v9 ...

From reading the publib doc: Tutorial for native XML data store

"You can create tables with XML columns only in databases defined with
the UTF-8 code set and a
compatible territory code."

But looking through the migration task(s), there is no mention of
changing DB code sets.
What is the envisioned method to enable XML features into existing DB2
v8 sites?
Should a hybrid dual-DB configuration be employed, or better to first
migrate v8 DBs to UTF-8 code set?

The strategy as I see it right now is to move to UTF-8 in the long haul.
Migration (I prefer the word upgrade myself) typically involves enabling
a DB on an old release to a new release without exploiting new features.
That's why you will find no mention in the docs on UTF-8 due to XML.
If you have existing DBs and you cannot/want not move them to UTF-8 at
this time, yet you want to start exploiting XML I would look into a
separate DB indeed.
For new applications starting of in UTF-8 may be in order.

In a future version I'd expect that a unicode db will provide a superset
of the capabilities as non-unicode and a whole sale move to UTF-8 will
be recommended in it's own right (with or without XML as added incentive)

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Apr 6 '06 #4

P: n/a
hi Serge,

I tried to instal the new version of Db2(Viper)..But it fails
saying that I have db2 version 7 in my system and asks me to uninstal
the older version, where as I dont have dv2 v7 installed at all..i had
v8.2 which I had uninstalled long time back.
~ Tariq Rahiman

Apr 20 '06 #5

P: n/a
rAinDeEr wrote:
I tried to instal the new version of Db2(Viper)..But it fails
saying that I have db2 version 7 in my system and asks me to uninstal
the older version, where as I dont have dv2 v7 installed at all..i had
v8.2 which I had uninstalled long time back.

Best post your question here:
http://www-128.ibm.com/developerwork...rum=842&cat=19

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Apr 20 '06 #6

This discussion thread is closed

Replies have been disabled for this discussion.