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.

• 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

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.

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

DB2 UDB:

CREATE PROCEDURE Grant_TablePermissions (
                            IN  oschema  varchar(20),
                            IN  permissions varchar(30),
                            IN  grantee varchar(30),
                            OUT  counter  smallint
                            )
    DYNAMIC RESULT SETS 1
P1: BEGIN
     DECLARE vstmt varchar(3000);
     DECLARE vname varchar(30);
     DECLARE vcounter smallint default 0;
     DECLARE at_end smallint default 0;

    DECLARE cursor1 CURSOR WITH RETURN for
        SELECT NAME FROM SYSIBM.SYSTABLES
            WHERE CREATOR = oschema ORDER BY NAME;

    DECLARE EXIT HANDLER FOR NOT FOUND
      SET at_end = 1;

    SET at_end = 0;

    OPEN cursor1;

    fetch_loop:
     REPEAT
       FETCH cursor1 INTO vname;
       SET vstmt = ‘grant ‘||permissions||’ on ‘||oschema||’.'||vname||’ to ‘||grantee;
       PREPARE s1 FROM vstmt;
       EXECUTE s1;
       SET vcounter = vcounter + 1;
       SET counter = vcounter;
     UNTIL at_end = 1
    END REPEAT fetch_loop;

CLOSE cursor1;   

END P1

SQL Server:

CREATE procedure [dbo].[Grant_TablePermission]
@permissions varchar(30),
@grantee varchar(30)
as
begin
       declare    @sqlcmd nvarchar(4000);
       declare    @tablename nvarchar(50);
       declare    @RowCount int;

      select @RowCount = 0;
      declare tablecursor insensitive cursor for
         select name from sys.tables

      open tablecursor;
      fetch tablecursor into @tablename;

      while (@@FETCH_STATUS = 0)
         begin
           select @sqlcmd = ‘GRANT ‘ + @permissions + ‘ on dbo.’+ @tablename + ‘ TO ‘+ @grantee +’;';
           execute sp_executeSQL @sqlcmd;
           print @sqlcmd;

           set @RowCount = @RowCount + 1;

           fetch tablecursor into @tablename;
      end;

        close  tablecursor;
        deallocate tablecursor;

    SELECT ‘Number of tables permissions has been granted: ‘ + CONVERT(varchar, @RowCount)

END

Here is how to send an email :

mailx -s “Subject goes here” “toemail@address” “body goes here”

mailx -r “sender@emailaddress” -s ”Subject” “toemail@address” “body goes here”

If the body is on a file :

mailx -s “Subject goes here” “toemail@address” < body.txt

If you want to send an attachment in the file :

uuencode data.csv data.csv|mailx –s “Subject goes here” “toemail@address”

If you want to send an email with body and attachment :

uuencode data.csv data.csv > datafile.csv  
cat body.txt datafile.csv > combined.file
mailx -s “Subject goes here” “toemail@address” < combined.file

The above three lines of code will enable you to send an email with body and an attachment.

declare c1 cursor select * from ds1.sales;
load from c1 of cursor messages load_sales.msg insert into ds1.sales_stage;

So what if you have to load data from another database (same server or different server) ?  First you need to catalog the remote database on the server and then you can declare a cursor for a remote database and then load using that cursor. Eg:
Assuming you have cataloged the source database on the target server as srcdb

connect to targetdb;
declare c1 cursor database srcdb user user1 using secretpass for select * from ps1.sales;
load from c1 of cursor messages load_sales.msg insert into ds1.sales_stage nonrecoverable;

This will load the data on table ps1.sales from the srcdb to ds1.sales_stage on the targetdb eliminating a file extract and then a load from the file.

_{* If the video is not clear please change the resolution on the youtube video to 1080p and view it full screen.}

Things to remember is :

1. You need database mail configured with an smtp server that the sql server can reach.
2. Setup Operator(s) for the SQL Server Agent to use for notification
3. Enable Mail Session on SQL Server Agent’s Alert System.
4. Enable notification on SQL Server Agent jobs to use the appropriate Operator profiles to send out emails.

Microsoft SQL Azure is one such database that is on the cloud.  Microsoft has made avalaible their proud SQL Server as part of your windows azure cloud offering.  With SQL Azure, you can create your own SQL server instances and databases for your applications. It can be accessed by other application fabric either on the cloud or from your own internal infrastructure.  Microsoft has two different versions of the SQL Server on the Azure platform : Web and Business.  Each of those again come in different sizes and options.  You can manage the sql server instance either via the management portal or from your favorite SQL Server management tool.   The cost is based on the usage of their windows azure usage.  There is a nice little price estimator that you use to determine how much it might cost you.

In this video I will walk you through on how to setup a free trial SQL Azure account and create your first SQL Azure database :

Apart from the above video Microsoft also has few videos that will give you in-depth knowledge of Windows and SQL Azure.