Skip to main content

DB2 Editions

This is a little bit off topic for me but on Friday I was asked to look at a DB2 instance and sort out some issues with the CPU maxing out. Make no mistake I’m no DB2 expert, but I have done some small pieces of work on it previously, and about a year ago I started making some notes . I’m going to turn these notes into blog posts, this will help my learning and give a place to reference and maybe it will help someone else out on the way.

DB2 like SQL Server has a series of edition with different features available in each one, here are some notes on the DB2 editions:

DB2 Express C – Full functional version of DB2 that is free to download use and distribute. The C stands for Community.

DB2 Express edition – Similar to the Express C version but there is a cost for support for this edition. It is designed for a quick installation and subsequent use. It supports 2 CPUs and 4GB of RAM. It can run on Linux, Windows and Solaris.

DB2 personal edition – Designed for single user use, It frugal with resources.

DB2 Everyplace 9 – For on a range of devices, PDAs, mobile phones etc. Ideal for distributed applications.

DB2 Workgroup Edition – Allows 4 CPUS and 16GB RAM

DB2 Enterprise edition – DB2 unleashed. No limits

DB2 developer edition – Enterprise edition features for the developer.

DB2 Datawarehouse Edition – has features to support DW environments.

So that’s it, my first post on DB2 looking at the available editions, there will be some further posts to follow when I get chance to turn my notes into posts.

Comments

  1. Great idea Gethyn. As Data Professionals we are often tasked with working on data issues in general and they may not always fall within our primary area of expertise.

    I for one am always keen to learn more about other database technologies so would certainly be interested to read about your findings.

    ReplyDelete
  2. Thanks John I probably have enough notes for a couple of posts.

    ReplyDelete
  3. I agree with John - always good for a DBA to widen their horizons !

    ReplyDelete

Post a Comment

Popular posts from this blog

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

New in SQL Server 2017: Graph Databases

David has recorded and published a video of his presentation on SQL Server Graph Database. In his video which you can watch below, David provides an excellent introduction into SQL Server 2017 Graph Databases. In his presentation he looks at Tennis results at tournaments for  his favourite player "The Fed"  Rodger Federer.

David  shows how to set up graph database and work with them in SQL Server 2017.

Graph Database is not new. Other vendors have had graph database capabilities for some time so Microsoft are quite late to the market. In David presentation it appears that Microsoft have done a reasonable job of implementing some of the graph database features but he does point some of the limitations of the Microsoft product too and suggests that it is not ready for production yet but Microsoft seem serious about this feature.

Please watch the video and feel free to leave a comment or feedback - David is delivering a version of this talk on Graph databases in SQL Saturday Ka…