Gotcha when restoring database with restrictive access !

Starting from DB2 V9.1, IBM added a parameter on the CREATE DATABASE command called RESTRICTIVE.   When this parameter is specified nobody other than the userid creating the database gets any implicit access to the database.  The database is automatically in a ‘locked down’ state.  This is great for businesses that don’t like giving access to their databases by default. As a production dba, I love it. Only the users that needs to access the database can be granted any access. Very controlled environment. I am sure most of the dbas out there would agree with me.

Restrictive doesn’t effect the SYSADMIN, DBADMIN, SECADMIN in anyway as long as they are in the right group. You can perform any functions within the database, within the same instance, until you decide to restore the database onto a different instance.  When you restore it to a different instance db2 does not automatically give the new instance owner or the userid/group the dbadmin privelege.  This means, you might lose admin privileges against that database. I am not sure whether its by design or a bug ?  I have opened a PMR with IBM to confirm.

What you can do is, login with a userid that has dbadmin or secadmin privilege on the original database and then give the new instance or new dbadmin user or group dbadmin group.

Posted in database, db2, how to | Tagged , , , , , | Leave a comment

DB2 10 arrives !

IBM announces DB2 10 for Linux Unix and Windows !  Code named Galileo, DB2 10 arrives with some neat features. We all know DB2 V9.7 was loaded with features, especially with Oracle compatibility. IBM has improved upon the Oracle compatibility mode making it almost 98%.
DB2 10 for LUW should be available for general electronic download on April 30, 2012 and for media order on June 11, 2012.
As usual the new DB2 is feature rich. IBM has packed some neat features on DB2 10. Among them some key ones are:

  • Adaptive Compression
  • Time Travel Query
  • Enhanced security
  • High performance warehouse features (Zigzag join)
  • Multi Temperature data management
  • Enhanced Workload Tuner
  • Continuous data ingestion
  • DB2 pureScale(enhancements)

IBM has also made changes to features available on DB2 editions.

Summary of DB2 10.1 edition changes:

Resource limits for each edition, where applicable, are also listed below.

DB2 Express-C:

  • Time Travel Query.
  • IBM Data Studio.
  • Memory limit has been increased to 4 GB. Processor core limit has been increased to two. Both limits are per physical server, or where partitioned, virtual server.

DB2 Express Edition:

  • Row and Column Access Control.
  • Label Based Access Control
  • Time Travel Query.
  • High Availability Disaster Recover (HADR).
  • IBM Data Studio.
  • Memory limit has been increased to 8 GB. Processor core limit remains at four. Both limits are per physical server, or where partitioned, virtual server.

DB2 Workgroup Server Edition:

  • Row and Column Access Control.
  • Label Based Access Control.
  • Time Travel Query.
  • IBM Data Studio.
  • Memory limit remains at 64 GB. Processor core limit remains at 16. Both limits are per physical server, or where partitioned, virtual server.

DB2 Enterprise Server Edition:

  • Row and Column Access Control
  • Label Based Access Control
  • Time Travel Query
  • Multi-Temperature Data Management
  • IBM Data Studio

DB2 Advanced Enterprise Server Edition:

  • Row and Column Access Control
  • Label Based Access Control
  • Time Travel Query
  • Multi-Temperature Data Management
  • Storage Optimization Feature, including Adaptive Compression
  • Continuous Data Ingest
  • IBM Data Studio
  • InfoSphere Data Architect (10 users)
  • InfoSphere Optim Configuration Manager
  • InfoSphere Optim Performance Manager Extended Edition
  • InfoSphere Optim Query Workload Tuner
  • InfoSphere Optim pureQuery Runtime for LUW

IBM Database Enterprise Developer Edition:

  • Row and Column Access Control
  • Label Based Access Control
  • Time Travel Query
  • Multi-Temperature Data Management
  • Storage Optimization Feature, including Adaptive Compression
  • Continuous Data Ingest
  • IBM Data Studio
  • InfoSphere Data Architect
  • InfoSphere Optim Configuration Manager
  • InfoSphere Optim Performance Manager Extended Edition
  • InfoSphere Optim Query Workload Tuner
  • InfoSphere Optim pureQuery Runtime for LUW

Here is a link that gives you a more in-depth look at the features

 

Posted in database, db2 | Tagged , , , , , , , , , , , | Leave a comment

SQL Server 2012 Licensing model

With SQL Server 2012, Microsoft has changed its licensing model along with “consolidating” the different types of editions. Gone is the workgroup edition. The three mainstream editions Microsoft now offers  are Enterprise, Business Intelligence and Standard . The Web Edition will be offered only to hosters via the Services Provider License Agreement (SLPA).  Developer, Express and Compact Editions will also continue to be distributed without licensing or pricing changes. Well Express edition is free. However the Developer, express and compact editions are not published in the Microsoft website.

Microsoft has also strategically changed from the previous processor based licensing model to a core based licensing model. So what does this mean, previously if you have a 2 processor server irrespective of the number of cores you have or use, you can buy licenses for 2 processor. But now if you have a quad core processor and have 2 processors on a server, you have to buy 8 (2 x 4 core) core SQL Server license. Now this move would make sense if you are in a VM environment where you might have 6-8 processor on the server and you might have assigned only 2 or 4 cores to a SQL Server. But if you are on a dedicated SQL Server it might increase your upgrade cost. How ? Lets say I have a 2 quad core processor(8 cores in total) on a server, previously I had to buy 2 processor license. If I decide to replace the 2 quad core processor with a 2 octa-core processor (16 cores in total) I didn’t have to buy any new sql server license under the old licensing model). But now under the new licensing model, I have to buy another 8 core worth of license. So my cost of an upgrade have gone up. Microsoft , please explain how this is going to help me reach my ROI quickly ?

If you are in a VM environment, there are multiple options depending on the route you want to go. If you are in a sql server standard edition then either:
1. You can license each VM based on the actual number of virtual cores you are using. However you need to buy a minimum of 4 core license for each SQL Server VM. In other words even if you use 2 virtual core for the sql server, you need a 4 core license (go figure !).
2. You can buy a server license for each VM plus CAL license for each user.
But if you are in an enterprise edition then you can license the server by total amount of physical cores and then create unlimited amount of VMs.

For a failover, if the secondary server is a passive node and is not being used at all then it doesn’t have to licensed, but if any workload is run against it then must be fully licensed. Also if there is a third passive node, then the third node irrespective of whether its being used or not should be fully licensed.

The cost of the license has also gone up around 20-27%. I hope they don’t say the hike in gas price caused the license to cost more !

Here is are few useful links that explains the new license changes and model:
SQL Server 2012 Licensing Quick Reference Guide.
Licensing Datasheet and FAQ

Here is an ebook for Introduction to SQL Server 2012

Please let me know how people are coping with these changes and any comments.

 

Posted in database, how to, sql server | Tagged , , , , , , , , | Leave a comment

Denali is on its way !

Microsoft is coming out with a new version of SQL Server , codenamed ‘Denali’ a.k.a SQL Server 2012.  It boasts lot of new features.  I am not going to repeat all of them here now.

Go to Microsoft to see all the features.  Here is another site that talks about top 5 features.

I will definitely write in detail in few weeks. Right now I am taking a break

Posted in database, sql server | Tagged , , , , , | Leave a comment