You can also find us on Myspace & Last.FM

As for interviews and reviews that we feature so far:

Interviews:

Jim Gaven
The Craze
Honor Society
Republic of Letters
Lazyeye
Kendall Payne
Rosemary's Sons
AM
Days Difference
Elseworth
Lisa Redford
Carbon Leaf
Kill The Alarm
Chad Perrone
Fenix Tx
Patrick Park
Fiction Plane
Fedchenka
Syd
Mark O'Shea
Joe Hedges
Rooney
Dakota Fate
JJ Appleton
Francis Martin
the Tom Glenne 5.5
Ernie Halter
SLAB
Cordless
Alphaspin
Mike Finley

apart from the 4 reviews that are expected soon, we are also negotiating interviews with several other artists and bands, but none of these have yet been confirmed. I hope to get answers from these people soon and I will let you know!

Reviews:

(the italic reviews listed are to be expected (relatively) soon)

1 Giant Leap - 1 Giant Leap
2nd Place Driver - 2nd Place Driver [EP]
2nd Place Driver - Leave [EP]
2nd Place Driver - ...1
2nd Place Driver - The Hungry Ones
2nd Place Driver - Full Speed, Bare Naked
3 Doors Down - The Better Life
3 Doors Down - Away From The Sun
3 Doors Down - Another 700 Miles [EP]
3 Doors Down - Seventeen Days
3 Doors Down - 3 Doors Down
12 Stones - 12 Stones
12 Stones - Potter's Field
12 Stones - Anthem For The Underdog
30 Seconds To Mars - 30 Seconds To Mars
30 Seconds To Mars - A Beautiful Lie
39 Reasons - 39 Reasons [EP]
a balladeer - Rumor Had It [EP]
a balladeer - Panama
Aaron Lines - Living Out Loud
Aaron Lines - Moments That Matter
All She Wrote - Coshade
Alli Rogers - Always Eden
Alli Rogers - One [EP]
Alli Rogers - The Day Of Small Things
Alli Rogers - At Sea
Alli Rogers - You & The Evening Sky
Alphaspin - Through The Solar Waves
American Hi-Fi - American Hi-Fi
American Hi-Fi - The Art of Losing
American Hi-Fi - Hearts On Parade
Augustana - Midwest Skies & Sleepless Mondays
Augustana - Mayfield [EP]
Augustana - You'll Disappear [EP]
Augustana - All The Stars & Boulevards
Augustana - Can't Love, Can't Hurt [EP]
Augustana - Can't Love, Can't Hurt
Billy Boy On Poison - Sweet Mess [EP]
Blyss - Diff's Lucky Day
Chad Perrone - Used To Dream
Chad Perrone - Wake
Clockwork Noise - Myspace Tunes
Cordless - Something Real [EP]
Cordless - Bright Lights
The Craze - Introducing.. The Craze
The Craze - Get Up! [EP]
Dan Wilson - Free Life
David Beebee - dB²
David Beebee - David Beebee [EP]
The Fray - Reason [EP]
The Fray - How To Save A Life
The Fray - Live @ Electric Factory
Honestly - Have A Nice Life
Honestly - Ghosts Of A Brilliant Past [EP]
HoneyHoney - Loose Boots [EP]
Honor Society - The Green Light [EP]
Honor Society - A Tale Of Risky Business [EP]
Hotspur - Myspace Tunes
Hotspur - Beta
Hungry Hungry Hypocrites - Rock, Roll, Fire & Magic
JJ Appleton - 500 Moments
JJ Appleton - Uphill To Purgatory
JJ Appleton - Someone Else's Problem
JJ Appleton - Black & White Matinee [EP]
John Taglieri - Leap Of Faith
John Taglieri - Half & Half
John Taglieri - NOW!
John Taglieri - Wide Awake & Dreaming
Keaton Simons - Currently [EP]
Keaton Simons - Exes & Whys
Keaton Simons - Blink [EP]
Keaton Simons - Can You Hear Me
Keith LuBrant - Searching For Signal
Lazyeye - Lights In The Attic
Lifehouse - No Name Face
Lifehouse - Stanley Climbfall
Lifehouse - Lifehouse
Lifehouse - Who We Are
TMATSMM & God Is An Astronaut - Split 12" [Vinyl]
Matt Swachman - Uncharted Territory
Mike Finley - Mike Finley [EP]
Mike Finley - The Way We Are [EP]
Missing Leg Compartment - Myspace Tunes
Nephu Huzzband - Papers [EP]
Patrick Park - Loneliness Knows My Name
Patrick Park - Mondays In Spaceland
Patrick Park - Stickbirdsongs [EP]
Patrick Park - Everyone's In Everyone
Patrick Ryan Clark - Translation
Radiohead - Pablo Honey
Radiohead - The Bends
Radiohead - OK Computer
Radiohead - Kid A
Radiohead - In Rainbows
Republic of Letters - Spirit Or A Ghost [EP]
Rocco DeLuca & The Burden - I Trust You To Kill Me
Rosemary's Sons - Misery Loves Company
Rosemary's Sons - All In Hand
Rosemary's Sons - St. Eleanor's Park
Rosemary's Sons - "The Others" [working title]
Seven Mary Three - Day & Nightdriving
SLAB - Betray The Past.. Infect The Future
Snow Patrol - Songs For Polarbears
Snow Patrol - When It's All Over We Still Have To Clear Up
Snow Patrol - Final Straw
Snow Patrol - Live & Acoustic @ Park Ave
Snow Patrol - Eyes Open
Souls A Fuse - Under The Spotlight [EP]
Three Days Grace - Three Days Grace
Three Days Grace - One-X
the Tom Glenne 5.5 - .married
the Tom Glenne 5.5 - White Soul
the Tom Glenne 5.5 - Free Rock

reviews for (among others): Untyde, Making April, Dakona, Fiction Plane, Silkstone, Rooney, Erny Green, Solo, Radford, Steve Bertrand, Emerson Hart, Avion, Voicst, Racoon, Krezip, Days Difference, My Favorite Highway, Jim Gaven, Kill The Alarm, Leaf, Alamo Race Track, Little things that kill, Big City Rock, We The Living, T.E.A. & Marwood are expected to follow.

A classe executa ainda uma query em uma tabela X e um insert.

Baixe clicando aqui -> conecta.

Renomeie o arquivo de odt para .java. O wordpress não permite efetuar upload de .java então tive que renomear.

Editado: Segue aqui a segunda parte do exemplo. Um menu com várias opções (incluir, excluir, Listar, etc) e classes de conexão e manipulação de clientes em banco.

Enjoy.

História:

O nome DB2 foi dado para o Sistema de Gerenciamento de Banco de Dados que a IBM lançou em 1983 baseado em SQL/DS para seu mainframe. A principio o produto foi chamado System R que fora iniciado em 1978. O projeto DB2 começou no inicio dos anos 70 quando Edgar Frank Codd, trabalhando para IBM descreveu a teoria dos Banco de dados Relacionais e publicou sua teoria em Junho de 1970. Para aplicar o modelo, Codd criou uma linguagem de banco de dados relacionais que a chamou de Alpha. Entretanto, a IBM não acreditava no potencial das suas idéias, deixando-o fora da supervisão do grupo de programadores, que violaram diversas idéias fundamentais do modelo relacional de Codd. O resultado foi a linguagem SEQUEL, que depois foi mudado para seu acrônimo SQL porque SEQUEL já era uma marca registrada.

Por muitos anos, DB2 foi feito exclusivamente para rodar nos mainframes da IBM. Posteriormente a IBM introduziu o DB2 para outras plataformas de servidores, incluindo o Unix e o Windows, para então colocar no Linux e PDAs. Esse processo foi feito na década 90. A inspiração para os detalhes de implementação do DB2 vieram da linguagem DL/1 da IBM e do Sistema de Gerenciamento de Informações também dessa empresa. As novas versões já são avaliadas para OS/2 e é chamada DB2/2.

Na metade do ano de 2006, a IBM anunciou o “Viper”, o codinome do DB2 9 para computação distribuídas e para DB2 9 no z/OS. A empresa diz que o novo DB2 será o primeiro banco de dados relacional que armazena o XML nativo. Outros recursos incluem o desenvolvimento baseado em OLTP para computação distribuídas, o desenvolvimento baseado em Business intelligence e data warehousing para z\OS, mais recursos de auto configuração e auto gerenciamento, adição de recursos para a plataforma 64-bits (especialmente para z/OS), melhoria na performance do armazenamento estruturado para z/OS e a continuação da padronização do vocabulário da linguagem SQL entre z/OS e outras computação distribuídas.

Edições:

DB2 é vendida em diversos tipos de “edições” ou licenças. Pela escolha de uma versão com menos recursos, a IBM evita que os consumidores paguem por coisas que não iriam usar. Alguns exemplos de edição são a Express, Workgroup e a Edição Enterprise. A edição mais sofisticada para Linux/UNIX/Windows é o DB2 Data Warehouse Entreprise Edition, ou DB2 DWE.

DB2 para Z/OS é vendido em sua próprio licença. Começando com a versão 8, a IBM vendeu o DB2 para z/OS e outros sistemas com característica muito próximas.DB2 para esse sistema tem algumas característica exclusivas: Segurança Multi-Level, tabelas de tamanhos extremamente grandes e compressão a nível de hardware. DB2 para z/OS foi sempre conhecido pela sua liderança de performance OLTP e é usado para suportar missões críticas nas operações de negócios, mas agora a versão z/OS está começando a adquirir característica Business intelligence.

Em 30 de Janeiro de 2006, a IBM lançou uma versão do DB2 chamada DB2 9 Express-C. Essa foi a resposta para os recentes pronunciamentos de versões gratuitas do Oracle e da Microsoft SQL Server. Express-C não terá limite no número de usuários e do tamanho do banco de dados. Foi desenvolvido para máquinas com sistema Windows e Linux até 2 processadores e até 4GB de memória.

Competição:

Historicamente, a primeira posição entre os SGDB do mercado foi marcado pela alternância entre DB2 e Oracle. Entretanto há outros SGDBs concorrentes como o Microsoft SQL (que é apenas disponível no Windows) além de sistemas de código aberto tais como o PostgreSQL, MySQL e Firebird. O DB2 para z/OS tem poucos concorrentes diretos, mas a Oracle tem atraindo consumidores para o Linux da zSerie, embora não as custas do DB2.

Em 2006 a IBM entrou na competição pelo emergente mercado de armazenamento warehouse aplicado ao mercado financeiro, com o lançamento de uma linha de produtos com sistemas de hardware/software pré-configurados. Essa família de “aplicações warehouse” foi nomeada como IBM Balanced Configuration Unit, ou BCU.

Informações Técnicas:

DB2 pode ser administrado tanto em uma interface de comandos de linhas ou em um ambiente gráfico. A interface de comando de linha requer mais conhecimento do produto mas pode ser mais facilmente automatizado. O ambiente gráfico é uma multi-plataforma Java que contem uma grande variedade de wizards para usuários iniciantes.

DB2 tem APIs para .NET CLI, Java, Python, Perl, PHP, Ruby, C++, C, REXX, PL/I, COBOL, RPG, FORTRAN, e muitas outras linguagens de programação. DB2 também tem suporte de integração no Eclipse e no Visual Studio .NET

- DB2 Express C
- Postgres no Ubuntu 8.04
- Tomcat via arquivo ZIP em Ubuntu 8.04
- RAD 7
- WebSphere App Server CE
- WebSphere App Server Enterprise

Baixe aqui.

Aguardem mais novidades ainda essa semana.

Por favor, critiquem a vontade!

Enjoy

• Develop and design critical financial system links and code enhancements to enable the creation of business reports for operational quality measurement and business controls
• Develops and designs critical interfaces between business applications and inputs to IBM Content Manager allowing the deployment of Content Manager globally
• Design, development, installation and support of Kofax Ascent Capture specific applications including XStrata Pro using standard Application Programming Interfaces
• Complex interface design between Content Manager and multiple applications
• Cross application development via DB2
• Polyglot skills in Java, VB, C++ program design, development and documentation skills
• Websphere Application Server application management and monitoring
• Supporting Customer requirements for related application development and change requests eg. TCS (Throw Catch System – Image)

Core Technical Skills Required:

• IBM Content Manager
• C/C++ 
• C#
• JavaScript
• Java
• Visual Basic
• Database experience in DB2
• Kofax Ascent Capture 7
• IBM Lotus Notes
• IBM WebSphere MQueue
• Kofax XStrata Pro OCR
• IBM Rational Application Developer
• VB.NET
• SQL
• XML
• HTML
• QMF
• TSO
• IBM CAPD    

Required:  

• Technical Diploma
• At least 5 years experience in General and wide IT skills
• Certified in IT
• English: Intermediate

Preferred:      

• Master's Degree in Information Technology
• English : Fluent            

Ele funciona por linha de comandos e tem janelas de auxilio. É criado para auxiliar principalmente desenvolvedores que se utilizam de SQL e serve para ser levado em qq pendrive para qq lugar, auxiliando a quem tem que acessar todo tipo de banco em vários lugares que nao se sabe qual recurso tem.

A primeira vista vai ser um programa simples, por linha de comandos, tendo bastante características que auxiliam na sua utilização.

Até agora, a melhor ferramenta de SQL que jah utilizei foi o Oracle SQL Developer, que está em sua versão 1.5, mas este não é o meu foco.

O primeiro passo interessante que tomei com o shibSQL foi o de tornar um JTextArea um InputStream, com o jline (http://jline.sourceforge.net/), e com isto criar algo levemente parecido com o bash do linux, com history e auto-completation e tudo !  Isto sim ficou legal, pq pode ser utilizado para qq intúito.

Bom, sem mais delongas, o trabalho ( seja bom, ou seja ruim ) será visto e avaliado por todos no seu decorrer. E a definição inicial, o esboço do que quero fazer está no meu wiki:

http://www.berlotto.com/wiki/index.php?title=ShibSQL

Há, e um logo ainda será criado ... hehehehe

Pois bem, encontrei um link muito bom no developer works que mostra como implementar a mesma em seu banco de dados.

Aqui está o material: http://www.ibm.com/developerworks/db2/library/techarticle/dm-0605singh/

Ainda para quem gosta de banco de dados, não necessariamente DB2, recomendo dar uma olhada em meus posts anteriores aqui -> http://jmmwrite.wordpress.com/category/db2/

Enjoy!

...download here: ibm_db2_common_store_for_sap

1.) Create a database in DB2 V9.5. Use the following command:

create database alfresco using codeset utf-8 territory us pagesize 32768

Of course, you can change the database name from alfresco to whatever you like.

It is possible to use a smaller default page size and create an additional table space with large 32K pagesize for bigger tables, but I've decided not to bother with that. This way I got Alfresco to create the tables and indexes by itself making the whole setup upgrade friendly.

2.) Create Alfresco extensions folder by creating a folder named lib/alfresco in your WAS profile folder. For example, in my profile called production1, the folder is:

/opt/IBM/WebSphere/AppServer/profiles/production1/lib/alfresco

Next, add the extension folder from the Alfresco war distribution into the lib/alfresco folder.

3.) Add the DB2 driver into the lib folder. The lib folder I'm referring to is the lib in lib/alfresco...

4.) Add the Alfresco extension folder to the ws.ext.dirs variable. To do this, open WAS admin console and go here: Servers -> Application servers -> pick you server (server1) -> Server Infrastructure -> Java and Process Management -> Process Definition -> Java Virtual Machine -> Custom Properties

Add a property named "ws.ext.dirs" and put the lib/alfresco (full path) in here.

5.) Restart WAS

6.) Install the Alfresco war archive. I've specified "alfresco" to by my context root, turned on JSP precompiling and used defaults for all other settings.

After the application is deployed, don't start it just yet!

7.) Set Alfresco application class loader properties to be:

• Classes loaded with the application class loader first
• Single class loader for application

You do this by opening the application properties in the WAS console and then click on the "Class loading and update protection" link. WAs won't allow you to save the new configuration if you leave the Pooling interval field blank. Just put 0 in there and all will be fine.

8.)  Remove the xml-apis.jar from the alfresco WEB-INF/lib folder.

9.) Modify the custom-repository.xml file in the Alfresco extensions folder to include the information necessary to connect to DB2. In my case the properties look like this:

db.driver=com.ibm.db2.jcc.DB2Driver
db.url=jdbc:db2://localhost:50095/alfresco
db.username=i95usr1
db.password=********

You can now run Alfresco...

“When I think back on the early days of development when we were all programming in DOS, and then take a look at what we can do now with technologies like the .NET Framework, it simply amazes me how far we’ve come,” Gates said. “I started out as a developer and that’s what I remain at heart, so I have a personal interest in the future of the field. I am confident that the path we are laying out today will serve you well into the future.”

Microsoft also made several announcements at this Orlando event, of particular interest was the technical collaboration with IBM.

An alliance with IBM that will further simplify application development for enterprise teams working in heterogeneous environments. IBM and Microsoft have agreed to work together to integrate IBM DB2 database access with Visual Studio Team System Database Edition.

The image in this post is of Bill Gates receiving a life time subscription to Xbox live for use after his retirement from a virtual Steve Ballmer embodied in a robot. Pretty niffty. I also hear that Tech Ed New Zealand was sold out in about three weeks with tickets gone by end of May, very cool.

1. I am biased and
2. I actually like Oracle XE but I like DB2 Express-C more ... see point 1

Now that I got this off my chest, I wanted to do a quick comparison between these two products from the two leaders in the commercial database server market. Both DB2 Express-C and Oracle XE (Express Edition) have much in common. Both are built on the same code that their very popular and at times expensive commercial counterparts are. Both can be downloaded and used for free to build applications, deploy them in production and even distribute as part of your application. Both DB2 Express-C and Oracle XE claim that you can build your application on them and when you "grow up" and need to scale you can upgrade to a paid edition without expensive recoding and migration of your application. So, what's the diff?
To be net, the biggest difference is that Oracle XE restricts you to storing maximum of 4GB of data. In my not so humble opinion this is an absolute joy killer. How can you use a product that limits how much data you an collect and stops in its tracks if you go over the limit. Say you are an ISV and you bundled Oracle XE in to your application and distributed to your customers. Now imagine your embarrassment and your customers' "emotion" directed at your support staff when your application just stops working because they stored more than 4GB of data. You may say "yeah Leon, you are full of it. 4GB is a lot." Bill Gates once said that nobody would ever need more than 64MB or RAM. For the record, I have 3GB of RAM in my laptop and with all due respect for Mr. Gates, I do need it all of it. But I digress. What is 4GB of data? How about just 2 BLOBs with pictures or a couple dozen or so scans of your purchase orders, invoices and other business documents. What about your digital media library. I have 1TB NAS at home and it is starting to fill up with pictures, home movies and iTunes stuff (yes, all legal; I am glad you asked :-)). iTunes library is in XML and DB2 Express-C does XML really well ... more on that later. 4GB is half of a decent memory stick. 4GB is nothing in our digital age. DB2 Express-C has no limit on how much data you can store. If you the disk space it will use it. Gigabytes, terabytes maybe even petabytes.
A few less dramatic points. Oracle XE runs on 32-bit Windows and Linux. DB2 Express-C does both 32 and 64-bit Windows and Linux but it also runs on Solaris X86. And for those with System p or System i servers, it is also a choice for running on Linux partitions on these servers. These POWER processors can give you a lot of oomph. So, if you have an System i (AS/400 for old timers) you can install DB2 Express-C on a Linux partition and get blazing fast replication of your AS/400 data in to DB2 Express-C. And did I mention that DB2 Express-C is available in 64-bit versions while Oracle XE is 32-bit only?
Speaking of hardware resources. Both Oracle XE and DB2 Express-C can be installed on any size machine be that a laptop with a single processor and 1GB of memory (3GB in my case) or a good size server with 4 multi-core CPUs and 16GB of memory. That's nice! Both products will use up to a set amount of hardware resources though. Oracle XE will use a maximum of 1 processor and will not allocate more than 1GB of memory. DB2 Express-C will go for double that. It will schedule its work on 2 processor cores and will allocate maximum of 2GB of memory. However, if you were to purchase optional subscription you can double resource allocations to 4 processor cores and 4GB of memory. And remember, there is never any restriction on the amount of data you can store. An astute reader may be wondering about the usefulness of the 64-bit version of DB2 Express-C in a 2GB or even 4GB environment. If you are wondering, read my blog post on the subject. So, DB2 Express-C can take advantage of 2-4 times the hardware resource when compared to Oracle XE. But what does this really mean? Well, by itself it means nothing. However, when you consider the fact that for database performance having extra memory is probably the most important aspect you understand that you have a potential of much higher performance with DB2 Express-C. What is more important is not only DB Express-C can take advantage of more memory when available it also needs much less memory to run. It turns out that Oracle XE is not quite the slimmed down version it claims to be. Here Windows task manager shows that while Oracle XE instance is up but is idle (not processing any queries) the commit charge is 1581MB

Now we stop Oracle XE instance

If you do a quick math you will see that just starting Oracle XE instance consumed about 600MB.

Let's get back to the code base. Both products use the same code base as their priced editions. However, Oracle XE is still at 10g R2 level despite the fact that 11g shipped almost a year ago. As a matter of fact, Oracle XE has not to my knowledge had any updates at all, not even for critical security flaws. DB2 Express-C on the other hand is constantly updated to the latest level of the DB2 code base. At this point in time it is v9.5 while initial release was v8.2. The free version of DB2 Express-C does not get Fixpacks but it is updated as the new releases of DB2 come out. However, DB2 Express-C does provide an option of low cost support delivered as a yearly subscription. If you were to purchase this subscription, you would get 24*7 support delivered by IBM engineers world wide. You also get double the resource allowance (4 processor cores and 4GB of memory), SQL based data replication and high availability clustering and off-site disaster recovery (HADR). Nothing like that is available with Oracle XE. If you are looking for data replication (Oracle Streams) you will need to move to Enterprise Edition ($47.5K per processor). Same is true for high availability (DataGuard). Even Oracle backup and recovery (RMAN) requires a move to Oracle Standard Edition One.

I saved the best for last. One of the really cool features in DB2 Express-C (and all other DB2 editions) is pureXML. Basically, DB2 Express-C database engine has hybrid data store. On the one hand, it is a very efficient high performing relational storage and query engine. On the other hand, it is also a storage engine that knows how to store parsed indexed XML trees in their native format and how to query data out of these trees using XQuery language. So, if you want to store your iTunes library in DB2 or maybe a large collection of insurance policy documents using industry standard ACCORD schema you can do so efficiently with full fidelity and be able to query these documents with the speed that you would expect from relational databases. It is really very fast.

As I said at the start of this post, I am naturally biased towards DB2 Express-C. However, I like to think that my bias is not just blind affection for my employer or the product I've been associated with for the last 15 years. I do feel that DB2 Express-C represents much better value than Oracel XE for anyone but a hobyist who is already well versed in Oracle. I just do not see how majority of peopel deploying real applcaitions can live with restriction on the amount of data their database can manage and such a low one to boot. Also, given memory consumption of Oracle XE and the very low 1GB memory limit, I am sceptical that one can expect perforamcne levels required for real world applcaitions. Last but not least, our IT peopel made me uninstall Oracle XE because it failed security vulnerability scans ... it is an unpatched 10g R2 version with dozens of well document vulnerabilities that I simply have no way of fixing. So, while I like Oracle XE for tinkering because it is much easier than other Oracle database editions, I don't see it being usefull for any kind of real life deployment.

Before I get in to the details, I wanted to just reemphasize that what you are reading here is NOT an official IBM position but an opinion that is mine and mine alone.

If you follow this blog than you already know that that IBM provides a product called DB2 Express-C which follows the now typical open source business model i.e. free license to use with available optional for fee service and support. It is important to note that "open source business model" is not the same thing as "open source" product. There are many definitions of "Open Source" and I can easily start a holly war on the subject here but I don't intend to; I am sorry if my definition of the "Open Source" does not comply with naming police requirements. In general, for DB2 to be considered open source we would have to make the source code available for download and inspection by anyone who wishes to do so and is able and willing to comply with the legal requirements of one of the commonly used open source licenses (a great subject of debate by many open source purists). It would typically also mean that IBM would be willing to receive contributions from the community in the form of code patches or even entire new modules and would not object to people creating completely new diverging branches of code. As I said before, I am playing fast and loose with the definition of the open source in an effort to explain what DB2 does or does not do.

Just to recap, DB2 is not available as open source. I can't comment with any degree of certainty on the future but my crystal ball is not showing open source plans for DB2. Over the years, IBM has shown great commitment to the open source movement by donating its technologies to the open source communities. In the database space, for example, IBM contributed Derby to Apache. So, we do open source big time. However, we do it judiciously and specifically when we have a strong belief that open source would provide great value to the community and the industry. At the time of release of DB2 Express-C we had extensive consultations with key customers and industry analysts. The feedback we were getting (and continuing to get) was that "open source" would not be beneficial. The number of people that would be interested in seeing DB2 source code can probably counted on 2 hands and half of those are likely to be our competitors. This is not a scientifically derived measurement but a general feeling. The number of people who would actually be able to contribute code is a small fraction of that at best. On the other hand we have a number of corporate customers who are very clear that they have great difficulties acquiring open source products. Corporate procurement departments will disallow open source product acquisition because of intellectual property concerns. Even when open source is grudgingly allowed, customers are demanding "Indemnification". Open source vendors such as MySQL had to respond by offering indemnification at (hefty?) extra charge. In the past suing MySQL was not a profitable proposition. It remains to be seen if now that MySQL is part of the SUN Microsystems, a company with much deeper pockets, this will still be the case.

What we did get a lot of input on is a desire to have a free DB2 product. Many of our customers as well as students, hobbyist and solution providers really like the ease of acquisition of the open source products i.e. no purchase orders, approvals, budgets etc. We on the other hand are very proud of our technology and want to get it in to as many hands as possible. We want everybody who ever touched XML to be able to experience the benefits of using DB2 pureXML and we don't want barriers such as lack of approved budget to stand in the way. So, you can download DB2 Express-C, full function real DB2 and we offer for free. You can build the latest wizbang (Web 1.0 term for term for "cool") Web 2.0 and Enterprise 2.0 applications with XML, web services, Atom, REST, SOA, Ruby on Rails, PHP, .NET, Java (and every other acronym you can think of) and deploy it for free. And if you need 24x7 support and backing from IBM you can get low cost (same price as MySQL Enterprise Gold) optional subscription. If you are in the business of building and selling software you can even bundle DB2 Express-C as part of your solution absolutely free. Our ISVs seem to like that a lot. They can now distribute an industrial strength commercial database as part of their offering without the legal concerns yet have the key benefit of open source. What they are not giving up on is the great technology and support that IBM can deliver 24 hours a day seven days a week in any corner of the globe in the language they speak. And this support is delivered by IBM and not subcontracted to a third party. It is delivered by exactly the same team that provides support for all other versions of DB2 and has complete access in to the engineers in our labs.

To sum this up "IBM may open source DB2" is a very catchy title for an article but it really does not represent our plans for DB2. IBM has contributed to the open source before and will continue to do so I am sure. But in my opinion there is no benefit in contributing DB2 to the open source. I believe that our partners and customers, and industry overall, is much better served by the current DB2 Express-C offering as it delivers the key benefits of open source without the downside that is typically associated with the open source.

Link

Once you click on "Proceed without an IBM ID" you will see a form like this one:

This is it. Hopefully you will find this process to be simpler and will encourage your friends and colegues to download and experience DB2 Express-C. And just as a reminder, it is completely free and has no time bombs or other annoying restrictions. 

Pēc pāris intermēdijām par to kā uzdot saprātīgu jautājumu un stāstu par to, ka vajadzētu padomāt kādus datus glabājam pie sevis un kādus dodam citiem internetā, paskatīsimies uz mazliet sausākām lietām. Oracle Merge SQL teikumu ir nodrošinājusi kopš 9i versijas, kas tika izlaista jau diezgan tālajā 2001 gadā. Sākumā tajā bija tikai UPDATE un INSERT klauzas, pie tam abas bija obligātas. 2003 gadā līdz ar versiju 10g MERGE funkcionalitāte tika papildināta pieļaujot neobligātu UPDATE, DELETE un INSERT. 11g versijā nekādi būtiski papildinājumi klāt nav nākuši.
Oracle Merge sintakse lielā mērā ir līdzīga SQL Server Merge sintaksei (kas vēl produkcijā īsti nav), bet tai ir savas atšķirības:
1) Nekur neparādās atslēgas vārdi TARGET un SOURCE;
2) Ierakstu dzēšana (Delete) ir zem Update operācijas, kas arī fiziski nozīmē, ka ieraksti vispirms tiek koriģēti un pēc tam iespējams izdzēsti, ja nosacījums to pieļauj.

Tātad sintakse ir šāda:

MERGE INTO <mērķa tabula>
USING <izejas dati>
ON (<salīdzināšanas nosacījums> )
WHEN MATCHED THEN <darbības, ja nosacījums patiess>
WHEN NOT MATCHED THEN <darbības, ja nosacījums aplams>

MERGE INTO <mērķa tabula>

Klauza neatšķiras no SQL Server MERGE INTO atbilstošās klauzas, tātad norāda tabulas vārdu kurā tiks koriģēti, dzēsti vai pievienoti dati.

USING <izejas dati>

Šajā klauzā tiek norādīts, no kurienes dati tiks ņemti. Pašā triviālākajā gadījumā šeit var norādīt vienkārši tabulas vārdu. Šeit var izmantot arī apakšvaicājumu un atsķirībā no SQL Server nav nepieciešams tam obligāti pievienot aliasu.

ON (<salīdzināšanas nosacījums> )

Klauza praktiski neatšķiras no SQL Server atbilstošās klauzas, vienīgais - sintaktisks smalkums - tā jāliek iekavās. Šeit paliek spēkā tieši tā pati lieta, kas iepriekš - MERGE teikums katru rindu mērķa tabulā var 1) vai nu koriģēt vai dzēst 2) darīt to ne vairāk kā vienu reizi. Tas nozīmē, ka nosacījumam ir jābūt tādam, ka katram ierakstam mērķa tabulā atbilst ne vairāk kā viens ieraksts izejas datos. Tiklīdz kā tādu būs vairāk, Jūs iegūsiet kļūdu.

WHEN MATCHED THEN <darbības ja nosacījums patiess>

Šī ir tā vieta, kur sākas atšķirības. Tātad šādu klauzu var rakstīt tikai vienu vienīgu reizi, taču tai var būt UPDATE daļa un DELETE daļa. Un tā izskatās šādi:

WHEN MATCHED THEN
UPDATE SET <update klauza>
WHERE <update where klauza>
DELETE <delete where klauza>

Šeit tiek rakstītas darbības (Update vai Delete), kas notiek tad, ja salīdzināšanas nosacījums ir izpildījies. Parastajā scenārijā (periodiska mērķa datu atjaunošana) tas nozīmē, ka mērķa tabulā ieraksti tiek koriģēti. Jāatceras vēlreiz augšminētais teikums "ieraksti vispirms tiek koriģēti un tikai pēc tam dzēsti", tātad no tā burtiski izriet, ka WHERE klauza, kas seko aiz UPDATE reizē ierobežo arī ierakstus, kas potenciāli tiks dzēsti - tātad DELETE tiek pielietota gan tam specifiskā WHERE klauza, gan arī UPDATE atbilstošā WHERE klauza, ja tāda eksistē.

Tagad beidzot ķeramies klāt pie piemēriem - tātad mums ir 2 tabulas, personals, kas būs mērķa tabula, un personals_src, kas tiks izmantota kā izejas datu tabula.

DROP TABLE personals;
DROP TABLE personals_src;
DROP SEQUENCE prs_seq;

CREATE TABLE personals (
pers_id INTEGER NOT NULL PRIMARY KEY,
prs_vards VARCHAR(40),
prs_uzvards VARCHAR(40),
prs_alga NUMERIC(10, 2),
prs_statuss VARCHAR(1));

CREATE TABLE personals_src (
vards VARCHAR(40),
uzvards VARCHAR(40),
alga NUMERIC(10, 2));

CREATE SEQUENCE prs_seq;

INSERT INTO personals VALUES
  (prs_seq.nextval, 'JĀNIS', 'BĒRZIŅŠ', 1234.56, 'S');
INSERT INTO personals VALUES
  (prs_seq.nextval, 'JĀNIS', 'KALNIŅŠ', 570, 'N');
INSERT INTO personals VALUES
  (prs_seq.nextval, 'PĒTERIS', 'ZIRNIS', 680, 'S');
INSERT INTO personals VALUES
  (prs_seq.nextval, 'MAIJA', 'ZINĪTE', 700, 'N');
INSERT INTO personals_src VALUES ('JĀNIS', 'BĒRZIŅŠ', 1200.00);
INSERT INTO personals_src VALUES ('JĀNIS', 'KALNIŅŠ', 400);
INSERT INTO personals_src VALUES ('ANNA', 'LEJA', 680);
COMMIT;

Izveidoto piemēru funkcionalitāte būs tieši tāda pati, kā analoģiskajam rakstam par SQL Server Merge teikumu.

Piemērs 1. Tabulas personals sākotnējie dati

SQL> SELECT * FROM personals;
PERS_ID PRS_VARDS PRS_UZVARDS  PRS_ALGA P
------- --------- ------------ ----------
      1 JĀNIS     BĒRZIŅŠ      1234,56  S
      2 JĀNIS     KALNIŅŠ      570      N
      3 PĒTERIS   ZIRNIS       680      S
      4 MAIJA     ZINĪTE       700      N

Piemērs 2. Ja darbinieka vārds un uzvārds sakrīt, tad koriģējam algu uz tādu, kā norādīta izejas tabulā. Šis Merge faktiski ne ar ko neatšķiras no vienkārša Update.

SQL> MERGE INTO personals
  2  USING personals_src
  3  ON (prs_vards = vards
  4    AND prs_uzvards = uzvards)
  5  WHEN MATCHED THEN
  6  UPDATE SET prs_alga = alga;
2 rows merged.
SQL> SELECT * FROM personals;
PERS_ID PRS_VARDS  PRS_UZVARDS   PRS_ALGA P
------- ---------- ------------- ----------
      1 JĀNIS      BĒRZIŅŠ       1200     S
      2 JĀNIS      KALNIŅŠ       400      N
      3 PĒTERIS    ZIRNIS        680      S
      4 MAIJA      ZINĪTE        700      N

Redzam, ka mainījusies alga pirmajam un otrajam ierakstam. Lai varētu veiksmīgi izpildīt nākošos piemērus varam atgriezties uz sākumu vienkārši izpildot ROLLBACK.

Piemērs 3. Ja darbinieka vārds sakrīt, tad koriģējam algu uz tādu, kā norādīta izejas tabulā. Redzam, ka nosacījums ir pārāk vājš un iegūstam kļūdu, jo atbilstoši šādam nosacījuma mērķa tabulā ieraksts ir jākoriģē vairākas reizes.

SQL> MERGE INTO personals
  2  USING personals_src
  3  ON (prs_vards = vards)
  4  WHEN MATCHED THEN
  5  UPDATE SET prs_alga = alga;
USING personals_src
      *
ERROR at line 2:
ORA-30926: unable to get a stable set of rows in the source tables

Kļūdas paziņojums, protams, ir savādāks nekā atbilstošais SQL Server piemērs, bet gala rezultāts ir tāds pats.

Piemērs 4. Ja darbinieka vārds un uzvārds sakrīt, tad koriģējam algu uz tādu, kā norādīta izejas tabulā gadījumā, ja darbinieks vēl strādā (statuss S). Ja darbinieks vairs nestrādā, tad dzēšam šādu ierakstu ārā.

SQL> MERGE INTO personals
  2  USING personals_src
  3  ON (prs_vards = vards
  4    AND prs_uzvards = uzvards)
  5  WHEN MATCHED THEN
  6  UPDATE SET prs_alga = alga
  7  DELETE WHERE prs_statuss = 'N';
2 rows merged.
SQL> SELECT * FROM personals;
PERS_ID PRS_VARDS  PRS_UZVARDS   PRS_ALGA P
------- ---------- ------------- ----------
      1 JĀNIS      BĒRZIŅŠ       1200     S
      3 PĒTERIS    ZIRNIS        680      S
      4 MAIJA      ZINĪTE        700      N

Redzam, ka tagad personals tabulā ir tikai 3 ieraksti, ar Delete ir izmests ārā tas ieraksts, kam statuss bija nestrādājošs.

WHEN NOT MATCHED THEN <darbības ja nosacījums aplams>

Tātad šī klauza izpildās tad, ja nosacījums ir aplams. Loģiski, ka tādā gadījumā mums tikai atliek datus pievienot.

Piemērs 5. Ja darbinieks nav mērķa tabulā, bet ir izejas datos, tad tādu pievienojam. Faktiski neatšķiras no vienkāršas Insert klauzas.

SQL> MERGE INTO personals
  2  USING personals_src
  3  ON (prs_vards = vards
  4    AND prs_uzvards = uzvards)
  5  WHEN NOT MATCHED THEN
  6  INSERT VALUES (prs_seq.nextval, vards, uzvards, alga, 'S');
1 row merged.
SQL> SELECT * FROM personals;
PERS_ID PRS_VARDS  PRS_UZVARDS  PRS_ALGA P
------- ---------- ------------ ----------
      1 JĀNIS      BĒRZIŅŠ      1234,56  S
      2 JĀNIS      KALNIŅŠ      570      N
      3 PĒTERIS    ZIRNIS       680      S
      4 MAIJA      ZINĪTE       700      N
      7 ANNA       LEJA         680      S

Redzam, ka nācis klāt jauns ieraksts, kas nebija iepriekš. Vairāk klauzu Merge teikumam Oraclē nav. Līdz ar to tiem cilvēkiem, kas ir izlasījuši rakstu par SQL Server Merge sintaksi varētu rasties pamatots jautājums - vai ir iespējams dabūt arī to funkcionalitāti, kas tika rādīta iepriekšējā rakstā, t.i., piemēram, tos ierakstus, kas nav izejas datos, bet ir mērķa datos, dzēst ārā? Ir iespējams, tikai šoreiz ir jārīkojas mazliet viltīgāk. Tas nav panākams triviāli, jo galvenais mērķis Merge teikumam ir lielu datu apjomu salīdzināšana un šajos scenārijos, katrā reizē normāli visa kopa netiek atjaunota, bet tiek atjaunota tikai kāda tās daļa vai arī likti papildus ieraksti klāt. Bet nu OK, kā tad to panākt? Jāmodificē mazliet izejas datu kopa. Atceramies, ka izejas dati var būt arī apakšpieprasījums - ne tikai vienkārša tabula - tātad jāmodificē apakšpieprasījums tādā veidā, lai arī tajā parādītos tie dati, ko vajag dzēst. Šeit noder FULL OUTER JOIN klauza, kas vispirms izejas datu tabulu savieno ar mērķa datu tabulu. Nākošajā piemērā skatamies kā pamazām tiek uzbūvēts nepieciešamais MERGE teikums, kurš dara šādas lietas:

• tiem darbiniekiem, kas ir abās kopās un strādā, tiek koriģētas algas;
• tie darbinieki, kas ir abās kopās un nestrādā, tiek dzēsti;
• tie darbinieki, kas ir izejas kopā, bet nav mērķa kopā, tiek tai pievienoti;
• tiem darbiniekiem, kas nav izejas kopā, bet ir mērķa kopā un statuss ir “strādā”, tiek uzstādīts jauns statuss “neskaidrs”;
• tie darbinieki, kas nav izejas kopā, bet ir mērķa kopā un statuss ir “nestrādā”, tiek dzēsti.

Tatad lai tiktu pie beigu Merge teikuma veicam to vairākos soļos:

• Vispirms izveidojam pilnu ārējo savienojumu abām tabulām;
• Tad balstoties uz to kā abās tabulās ir izvietoti dati uzstādam karodziņu;
• Visbeidzot izpildam pašu MERGE SQL teikumu.

Piemērs 6. Izveidojam apakšvaicājumu MERGE izejas datiem.

SQL> SELECT * FROM personals
  2  FULL OUTER JOIN personals_src ON
  3  (prs_vards = vards
  4    AND prs_uzvards = uzvards);
PERS_ID PRS_VARDS PRS_UZVARDS PRS_ALGA P VARDS  UZVARDS  ALGA
------- --------- ----------- -------- - ------ -------- ----
      1 JĀNIS     BĒRZIŅŠ     1234,56  S JĀNIS  BĒRZIŅŠ  1200
      2 JĀNIS     KALNIŅŠ     570      N JĀNIS  KALNIŅŠ  400
      4 MAIJA     ZINĪTE      700      N
      3 PĒTERIS   ZIRNIS      680      S
                                         ANNA   LEJA     680

SQL> SELECT nvl(vards, prs_vards) vards,
  2       nvl(uzvards, prs_uzvards) uzvards, alga,
  3    CASE WHEN vards IS NOT NULL
  4          AND prs_vards IS NOT NULL
  5          AND prs_statuss = 'S' THEN 'upd_alga'
  6         WHEN vards IS NOT NULL
  7          AND prs_vards IS NOT NULL
  8          AND prs_statuss = 'N' THEN 'del'
  9         WHEN vards IS NOT NULL AND prs_vards IS NULL THEN 'ins'
 10         WHEN vards IS NULL
 11          AND prs_vards IS NOT NULL
 12          AND prs_statuss = 'S' THEN 'upd_statuss'
 13         WHEN vards IS NULL
 14          AND prs_vards IS NOT NULL
 15          AND prs_statuss = 'N' THEN 'del'
 16    END karodzins
 17  FROM (
 18    SELECT * FROM personals
 19    FULL OUTER JOIN personals_src ON
 20    (prs_vards = vards
 21      AND prs_uzvards = uzvards)
 22  )
 23  /

VARDS   UZVARDS   ALGA KARODZINS
------  -------- ----- -----------
JĀNIS   BĒRZIŅŠ   1200 upd_alga
JĀNIS   KALNIŅŠ   400  del
MAIJA   ZINĪTE         del
PĒTERIS ZIRNIS         upd_statuss
ANNA    LEJA      680  ins

Piemērs 7. Izveidojam MERGE teikumu atbilstoši augšminētajam pilnajam algoritmam.

SQL> MERGE INTO personals
  2  USING (
  3    SELECT nvl(vards, prs_vards) vards,
  4         nvl(uzvards, prs_uzvards) uzvards, alga,
  5      CASE WHEN vards IS NOT NULL
  6            AND prs_vards IS NOT NULL
  7            AND prs_statuss = 'S' THEN 'upd_alga'
  8           WHEN vards IS NOT NULL
  9            AND prs_vards IS NOT NULL
 10            AND prs_statuss = 'N' THEN 'del'
 11           WHEN vards IS NOT NULL AND prs_vards IS NULL THEN 'ins'
 12           WHEN vards IS NULL
 13            AND prs_vards IS NOT NULL
 14            AND prs_statuss = 'S' THEN 'upd_statuss'
 15           WHEN vards IS NULL
 16            AND prs_vards IS NOT NULL
 17            AND prs_statuss = 'N' THEN 'del'
 18      END karodzins
 19    FROM (
 20      SELECT * FROM personals
 21      FULL OUTER JOIN personals_src ON
 22      (prs_vards = vards
 23        AND prs_uzvards = uzvards)
 24    )
 25  )
 26  ON (prs_vards = vards
 27    AND prs_uzvards = uzvards)
 28  WHEN MATCHED THEN UPDATE
 29  SET prs_alga = (CASE karodzins WHEN 'upd_alga'
 30                    THEN alga ELSE prs_alga END),
 31    prs_statuss = (CASE karodzins WHEN 'upd_statuss'
 32                   THEN '?' ELSE prs_statuss END)
 33  DELETE WHERE karodzins = 'del'
 34  WHEN NOT MATCHED THEN
 35  INSERT VALUES (prs_seq.nextval, vards, uzvards, alga, 'S')
 36  /

5 rows merged.

SQL> SELECT * FROM personals;

PERS_ID PRS_VARDS PRS_UZVARDS  PRS_ALGA P
------- --------- ------------ -------- -
      1 JĀNIS     BĒRZIŅŠ      1200     S
      3 PĒTERIS   ZIRNIS       680      ?
     19 ANNA      LEJA         680      S

Kā redzams, šis SQL Merge teikums izskatās diezgan garš un pirmajā brīdī varbūt nav nemaz tik vienkārši izsekot tam visam līdzi, bet galvenā ideja, ko atcerēties ir tāda, ka mazliet padomājot gala rezultātā šo visu diezgan sarežģīto algoritmu var paveikt ar vienu SQL teikumu.

Kas jāatceras papildus

• Kā jau tika minēts augstāk, katru rindu var koriģēt tikai vienreiz, tātad raugieties, lai salīdzināšanas nosacījums būtu pietiekami stingrs un vienam mērķa tabulas ierakstam atbilstu ne vairāk kā viens izejas tabulas ieraksts.
• Merge teikumā nedrīkst koriģēt salīdzināšanas nosacījumā ietvertās kolonas, citādi būs kļūda.
• Ja Jūs izmantojat sekvences Merge Insert klauzā, tad esat gatavi, ka tājās parādīsies potenciāli diezgan lieli "caurumi", jo sekvenču vērtības tiek ģenerētas katrai izejas kopas rindai pirms tiek noskaidrots, vai šo rindu pievienos vai koriģēs, vai nedarīs neko. Vairāk par to kā un kāpēc tas tā notiek var lasīt mana angliskā emuāra ierakstā SQL Merge and Sequence gaps. Normāli tam nevajadzētu radīt nekādas problēmas, jo sekvences tiek izmantotas tikai kā unikālu skaitļu ģeneratori un nekas vairāk.
• Merge teikums nestrādā, ja tiek izmantota Fine-grained access control (Oracle iespēja, kas lietotājam nemanot fonā piekārto SQL teikumiem papildus Where nosacījumus, kurus ir iespējams dinamiski izveidot).

Merge teikums citās DBVS

Merge teikums ir pieejams arī citās DBVS, piemēram DB2 un šķiet to taisās ieviest arī PostgreSQL. MySQL Merge teikuma nav, bet ir šai datubāzei specifiski SQL teikumi, kas nekur citur nav, piemēram, REPLACE un INSERT ... ON DUPLICATE KEY UPDATE un kas kaut kādā mērā var tikt pielietoti, lai daļēji simulētu Merge funkcionalitāti.

Tālākā lasāmviela

• Oracle Merge sintakse;
• DB2 Merge sintakse;
• SQL Server Merge sintakse;
• MySQL Replace sintakse;
• MySQL Insert ... On Duplicate Key Update sintakse.

MESSAGE : ADM1823E The active log is full and is held by application handle
"35". Terminate this application by COMMIT, ROLLBACK or FORCE
APPLICATION.

みたいなのが書かれてる。

現在の設定を確認
$db2 get db cfg for xxxxx

ログファイルのサイズ(4K) LOGFILSIZ=1024
1次ログファイル数 LOGPRIMARY=13
2次ログファイル数 LOGSECOND=4

になってる。
別に少なくないじゃんと思うが
まあ、出来ないのだからこの際仕方ないから
サイズを倍の8Mにした。

$db2 update db cfg for xxxx using LOGFILSIZ 2048

DB再起動

Linux環境では
export DB2OPTIONS=+c
って書いてあるが、win環境で環境変数を変えても
ちっとも変わらないので
これからは、事前に調べて
db2 +c ＳＱＬ文
って打たないとダメです。

O livro pode ser utilizado para ter uma boa introdução sobre o DB2. Recomendadíssimo!

O mesmo pode ser baixado gratuitamente daqui: http://www.ibm.com/developerworks/wikis/display/DB2/FREE+Book-+Getting+Started+with+DB2+Express-C

Enjoy!

ちょい面倒