| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WMB 8 - Client connectivity to App Databases |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Wed May 08, 2013 4:21 am Post subject: WMB 8 - Client connectivity to App Databases |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
The big three database platforms in our shop are Oracle, SQL Server and DB2.
WMB comes with built in connectivity to make client connections to Oracle and SQL Server databases, but not DB2. IBM makes DB2.
You would think IBM would make it easier / cheaper to connect to DB2 databases from WMB, to perhaps encourage more DB2 use. Am I missing something or is it really the case that ALL things being equal (and they never are, but....) its cheaper/ easier to have WMB talk to Oracle or SQL Server versus DB2 out of the box?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed May 08, 2013 4:35 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It's got naught to do with Broker.
DB2 requires a client install and a license model built on top of that.
Broker used to ship with all of the software you would need to establish DB2 connections, when Broker itself used DB2 internally. But it was never licensed for you to use that software to talk to application databases.
So the DB2 licensing model, and Broker's license model have not changed.
The only thing that has changed is that Broker stopped shipping with DB2 software. Because Broker doesn't need it for internal purposes.
Just because Broker ships with an ODBC driver for Oracle and SQLServer, that doesn't mean it grants you a license to connect to an Oracle db or an SqlServer DB.
And at least for Oracle, you may still choose to use the Oracle client install instead of relying on the thin client that the ODBC driver puts forth as default.
Broker doesn't make it more expensive or less expensive to connect to any database.
It makes the installation process and configuration process for some databases take less time (and therefore in theory less expensive). But that's only really if you accept the default settings. Your DBAs should still be spending time analyzing the necessary usages of the database connections, and the impact on licensing.
Oracle and SQLServer may make it cheaper to connect to their databases by not charging client-seat fees. But that's, again, got naught to do with Broker. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
