After upgrading from PDI 3.x to 4.0.1, I've found that the old way of exporting an repository subfolder in a single step is gone. It's still important for me to be able to do this since I use separate repositories for Development, Test, and Production, and these systems must remain isolated.

As a work around, here is what I am doing for now:


You can still keep your jobs and transforms organized in repository folders/sub-folders. But you have to now export each (open) job and transformation individually using File -> Export -> To XML

I just save these files to an empty temporary directory on the file system.

Then I disconnect from the source ( development) repository and connect to the destination repository, ( ie. Test or Production).

In there, use :

Tools -> Repository -> Import Repository

In the dialog that displays: …

Next Thursday Oracle University will be hosting a lunchtime webinar, between 13.00 and 14.00 CET, to help you better understand the common MySQL mistakes impacting performance that you should avoid.

Oracle's senior MySQL instructor and consultant Kai Voigt will review the MySQL "no no's" and advise on what simple solutions should be used instead. Kai will also provide an introduction to indexing, rewriting of queries, monitoring the use of temporary tables, and other things you should know about.

You can register here for this free webinar taking place on Thursday November 25th at 13.00 CET.

Next Thursday Oracle University will be hosting a lunchtime webinar, between 13.00 and 14.00 CET, to help you better understand the common MySQL mistakes impacting performance that you should avoid.

Oracle's senior MySQL instructor and consultant Kai Voigt will review the MySQL "no no's" and advise on what simple solutions should be used instead. Kai will also provide an introduction to indexing, rewriting of queries, monitoring the use of temporary tables, and other things you should know about.

You can register here for" this free webinar taking place on Thursday November 25th at 13.00 CET.

We are pleased to announce this new major release of SQLyog MySQL GUI.

The major enhancements with this release are:

* Information in tabbed interface can be reordered.
Just like you will find it in all modern browsers, TABs can now be reordered using drag’n’drop in the GUI. The option is available for connection tabs as well as Query/Query Builder/Schema Designer tabs.

* Fast and convenient data entry from the keyboard.
We have added ‘FORM view’ option (in addition to ‘GRID view’ and ‘TEXT view’ already available) for managing data in DATA and RESULT tabs. ‘FORM view’ will display one row at a time and is in particular convenient when entering data from the keyboard.

…

We need to test if MySQL can be reliable with huge data sets, talking of a daily waterfall of about 30 million INSERTs and a few daily analityc big SELECTs too.
So what's the deal ? which database engine ? which platform ? which architecture ? ... and is data secured ? accessible ?
Before choosing MySQL 5.1, i turned around these three databases:

• Oracle :
  Known as the 'most reliable' database engine in the world, personally i don't believe in that, and i didn't choose it for its cost (Especially that :) ).
  
• PostgreSQL :
  A good database engine, it succeeded where older than 5.0 versions of MySQL failed, but now, both engines are mature enough and i'm switching between them on every new projects depending on the specific needs of each project architectures.
  Switching between database engines should be a simple task when the application deploys an abstraction layer on …

It's entirely possible, given my propensity to swear and rant and declare things to be Web Scale, that folks might get the idea that I do not like our newer NoSQL bretheren. Quite the contrary - I think almost all of them are exciting and well suited to various tasks. My biggest beef is in thinking that a single technology should be square-pegged into every round-hole anyone can find. This holds true for Drizzle and MySQL as well, by the way. Just because I work on Drizzle does not mean I think Drizzle should be the method of data storage for every blessed thing on the face of the planet - that would be silly!

I bring this up because I had my first instance of thinking that Cassandra might be a good choice for a project someone was showing me yesterday. In this case, the project was collecting data about events, but it as the data was events about real-world interactions, the particular information stored about each collected event had the …

Loose index scan in MySQL can really help optimizing “group by” queries in some cases (for example, if you have only min() and/or max() as your aggregate functions). For example, if you have this query (to find maximum delay for all US flights with departure on Sundays in 2010):

select max(DepDelayMinutes),       carrier, dayofweek 
from ontime_2010 
where dayofweek = 7 
group by Carrier,  dayofweek

the usual case will be adding a covered index on (dayofweek, Carrier, DepDelayMinutes). And MySQL will use this index fine (using index mean it will use the covered index):

mysql> explain select max(DepDelayMinutes), Carrier, dayofweek from ontime_2010 
where dayofweek =7 group by Carrier, dayofweek\G
*************************** 1. row ***************************
           id: 1
  select_type: SIMPLE
        table: ontime_2010
         type: ref
possible_keys: covered
          key: covered
      key_len: 2
          ref: const …

Warning, this may be kernel version specific, albeit this kernel is used by many database systems

Lately I’ve been working on getting more memory used by InnoDB buffer pool – besides obvious things like InnoDB memory tax there were seemingly external factors that were pushing out MySQL into swap (even with swappiness=0). We were working a lot on getting low hanging fruits like scripts that use too much memory, but they seem to be all somewhat gone, but MySQL has way too much memory pressure from outside.

I grabbed my uncache utility to assist with the investigation and started uncaching various bits on two systems, one that had larger buffer pool (60G), which was already being sent to swap, and a conservatively allocated (55G) machine, both 72G boxes. Initial finds were somewhat …

This is the 150th tip published on this blog so decided to make it a collection of all the previous ones. Here is a tag cloud (created from wordle.net/create) from title of all the tips:

As expected GlassFish is the most prominent topic. And then there are several entries on NetBeans, JRuby/Rails, several Java EE 6 technologies like JPA, JAX-WS, JAX-RS, EJB, and JSF, and more entries on Eclipse, OSGi and some other tecnhologies too. Here is a complete collection of all the tips published so far:

• #149: How to clean IntelliJ cache, preferences, etc on Mac OS X ?
• …

Dealing with sql_mode can be a tricky business, and many people have blogged about it before (here and here). My intent is not to explain the details of what each option means (since it's covered in the manual), but rather to answer this simple and common question:
Which SQL mode should I use with MySQL? / What is the recommended SQL mode for MySQL?

My general purpose recommendation is this one:

sql-mode="TRADITIONAL,NO_ENGINE_SUBSTITUTION,ONLY_FULL_GROUP_BY"

This "traditional" setting includes most of what you'd want your database to behave like, namely:

STRICT_TRANS_TABLES, STRICT_ALL_TABLES, …