• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 870
  • Last Modified:

MV DBMS versus SQL Server or MySQL

Hi all,

I have been working with database systems for a while now, and I have been searching for a brief and to-the-point document on the benefits of using a multi-value database system over SQL Server or MySQL, with no luck.  Don't get me wrong, I love MySQL and tolerate SQL Server, but I am a big fan of IBM Universe.

I use either SQL Server or MySQL for numerous web applications.  This question is aimed more at large transactional systems such as ERP.

I'm putting this question up to get the input of others and put together a good pro's and con's document.  

Thank you in advance for your input.
0
Newco
Asked:
Newco
1 Solution
 
momi_sabagCommented:
why would you need a multi-valued database?

0
 
Raja Jegan RSQL Server DBA & ArchitectCommented:
>> I use either SQL Server or MySQL for numerous web applications.  This question is aimed more at large transactional systems such as ERP.

You need OLTP database for your requirement.
Why do you require OLAP ie, Multi valued or Multidimensional database for this requiement..

If your requirement differs, kindly explain so that it can be checked out..
0
 
NewcoAuthor Commented:
momi_sabag:
>> why would you need a multi-valued database?

In my opinion, a mv db stores data more efficiently for large transactional databases. It's not a direct 'need' for a mv system, more of a preference.

For example, if I have 7 phone numbers and 7 contacts for one customer, I would have 7 rows in a traditional sql table to store those phone numbers.  In a mv db, I would have one row in a file for that customer, and the contact_name field would have 7 positioned values, and the phone number field would have 7 positioned values.  Just a very simple (and probably very poor) example.

rrjegan17:
>> You need OLTP database for your requirement.
Why do you require OLAP  ie, Multi valued or Multidimensional database for this requiement..

I agree, there is a need for some sort of OLTP for systems such as ERP, etc - and IBM's products are usually considered the leader in that area.  However, a mv database usually has some sort of online transaction processing built in.  OLAP is not necessarily MV and vice-versa though.
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
momi_sabagCommented:
you could always use a database such as db2 or oracle and store your multiple values using a single xml value.
today, these database support xml data type in a way that allows you to index the content of the xml values so you can access each value directly
0
 
Anthony PerkinsCommented:
>>you could always use a database such as db2 or oracle <<
Or even MS SQL Server ... :)
0
 
dportasCommented:
>> mv db stores data more efficiently for large transactional databases

Multi-valued is a logical model of data. So is the SQL model. In either case I see no fundamental reason why the data *must* be stored more or less efficiently because neither model specifies how the data is to be stored.

Many SQL DBMSs have extremely efficient compression features so you cannot draw a conclusion that having more rows means more storage will be used. Also some SQL DBMSs use a column-store model of storage with quite different characteristics.

0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now