A simple way to export data from a query, table, etc.. of an oracle database to a flat file is to use the SPOOL command in SQLPlus. This would not need to rely on visual aids, which are not always available or do not always work as we want. Also you can use the Oracle format functions in the same SELECT statement that generated the data already in the format we need.

If, for example, we want to retrieve some data from all records in a table of customers sorted by date of discharge, simply open a SQLPlus session and run this series of commands: 

SQL> SET HEADING OFF
SQL> SET FEEDBACK OFF
SQL> SPOOL C:\datos_de_clientes.txt
SQL> SELECT 'Cliente ' || CLI_NOMBRE || ', ' || CLI_NIF || '. Fecha alta: ' || TO_CHAR(CLI_FECHAALTA,'YYYY-MM-DD')
FROM TABLA_CLIENTES
ORDER BY CLI_FECHAALTA DESC;
SQL> SPOOL OFF;
SQL> SET FEEDBACK ON
SQL> SET HEADING ON

The first lines hide the headers that contain the field name, and do not concern us because we only want the data. Spool directs the output of data to the file 'datos_de_clientes.txt' on the C drive on the local machine.

In batch runs to make a massive data dump into the same table using an INSERT or UPDATE for register within a block, the process can be optimized with the use of parameters (if client supports it) or if we use ODBC with bind variables.
Recall the steps taken by Oracle to process a query:
1) Sintactic Validation 
2) Semantic Validation
3) Optimization 
4) Generation of the QEP (Query Execution Plan)
5) Implementation of the QEP (Query Execution Plan)
Sentences can pick up the parameters by value (where salary > 1000) or once the sentence is compiled using Bind Variables (where salary>: b1). The advantage of the second option is that Oracle compile the sentence only one-time and reuses the compiled code for each of the values for the parameters.
But we must be aware because in the latter case because Oracle can't calculate the degree of selectivity of a query and, instead, apply a degree of selectivity by default (associated with each type of operation), which can give in wrong decisions.

SAP TechED presented in Vienna on Gravity product prototype, a BPM solution that works on the collaborative environment provided by Google Wave.

This product allows Business Process desing collaboratively, building communication facilities provided by the environment Google Wave. Obviously it works for web, and can also be used from mobile devices like an iPhone.

This video shows how to simulate a situation of merger of two companies in which they must redefine many business processess the highest level.

As many have noticed, we changed Dataprix logo.

Although the symbol of the head with the database during the previous logo reflected fairly well the spirit of Dataprix, and the relationship between data and knowledge, we believe it necessary to create a logo more 'professional', which will be the basis corporate image Dataprix.

Our primary corporate color is still blue, so the change on the web has not noticed too. We have changed the symbol for a 3D database, and D-shaped, to keep referring to the data, and lose the reference to knowledge that gave us the figure of a blue head, but you can not have everything in life ;).

In addition, we've heard from somewhere that may be better to simplify the meaning of the symbol to convey a clearer picture. For people not as technological areas, which need not recognize the symbol of a database could also be difficult to identify. On occasion I have come to discuss that on seeing the logo Dataprix seemed he might have something to do with a headache, or Bayer aspirin ..

As expected, the first BI tools adapted to the new iPad of Apple are appearing. Nothing like a dashboard application to exploit the Multitouch screen possibilities of this device.

Prelytis is the company that has developed Prelytis LiveDashBoard, the first Business Intelligence software compatible with the new Apple Tablet. This is a dashboarding tool, and 2.0 oriented, with collaborative features, and remarkable for their efforts in terms of adaptation to mobile devices.

This post is based on this one of il-masacratore:Time: Dimension structure and loading script for SQLServer. 

As il-masacratore says usually there are a number of dimensions that are common to all DW. The Time dimension is one of them. 

In a Data Warehouse there are a number of common dimensions such as Geographic and Time. 

I leave here a script to create the Time Dimension table and a procedure to loading it between two dates:

/ * Destination database * /

use PAnalisys