ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » MQSeries internal persistence on Oracle database ?

Post new topic  Reply to topic Goto page Previous  1, 2
 MQSeries internal persistence on Oracle database ? « View previous topic :: View next topic » 
Author Message
Vitor
PostPosted: Thu May 20, 2010 3:55 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

gbaddeley wrote:
To be pedantic, DBs use filesystems to store their data too.


People are shocked when I point that out as a counter to the "a DB is better than a file system to store queues" discussion.

One client actually dragged the DBA team into the debate in an attempt to prove I was talking rubbish.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
mvic
PostPosted: Thu May 20, 2010 4:12 pm    Post subject: Reply with quote

Jedi

Joined: 09 Mar 2004
Posts: 2080

gbaddeley wrote:
I can imagine that over many versions of MQ the file structure for storing queued messages and recovery logging has been highly optimised for reliability and performance (including get by msgid). There is no point in allowing MQ to use an external DB, it would slow it down and decrease the reliability, as an extra link would be in the chain.

To be pedantic, DBs use filesystems to store their data too.

Agreed. But discussing the precise means of data storage is a proxy for the age-old newbie MQ question: "why buy MQ rather than a database?".

So here we go again.

There is a basic difference between providing short-term buffering/transport of data and providing storage/query/quick-access to large amounts of data.

MQ can store data, but if you want to search and find that data based on its contents you ought to have processed it and stored it in a database.

MQ is a message transport first and foremost. It will store data for you, but that it not its main value proposition.

If storing/querying/accessing a set of data is the requirement, buy a database product.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Thu May 20, 2010 6:26 pm    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9482
Location: US: west coast, almost. Otherwise, enroute.

Quote:
- Databases are more resiliant than filesystems

WMQ uses database logging to ensure resiliancy.
Quote:
- We want to replicate the messages with database replication because <insert excuse>

There are many ways to do this with WebSphere and 3rd-party offerings, and w/o a database.
Quote:
- Doing a get by msg id will be faster

Relational databases are not known to be stellar performers. WMQ is performance-tuned to do what it does, including retrieving messages by msgid, correlid, groupid.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » General IBM MQ Support » MQSeries internal persistence on Oracle database ?
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.