background preloader

Home [LiquiBase]

Home [LiquiBase]

Oracle Date functions and parameters Oracle Date Functions Version 10.1 Date Current Date SELECT CURRENT_DATE FROM dual; SELECT SYSDATE FROM dual; Current Time SELECT CURRENT_TIME FROM dual; Formats J Julian Date -- Day -- Month -- Year -- Fill Mode Formats That Can Be Used With ROUND And TRUNC Functions - One greater than the first two digits of a four-digit year - Year (rounds up on July 1) - ISO Year - Quarter (rounds up on 16th day of the 2nd month of the quarter) - Month (rounds up on the sixteenth day) - Same day of the week as the first day of the year - Same day of the week as the first day of the ISO year - Same day of the week as the first day of the month - Day - Starting day of the week - Hours - Minute SELECT SYSDATE + 1 FROM dual; SELECT SYSDATE - 1 FROM dual; Add A Month To A Date ADD_MONTHS( , SELECT add_months(SYSDATE, 2) FROM dual; Returns the current date of the server as a value in the Gregorian calendar of datatype DATE col sessiontimezone format a30 SELECT sessiontimezone, current_date FROM dual; SELECT DUMP(SYSDATE) FROM dual; FROM t;

The 38 Subsystems of ETL -- InformationWeek Three little letters -- E,T, and L -- obscure the reality of 38 subsystems vital to successful data warehousing. The extract-transform-load (ETL) system, or more informally, the "back room," is often estimated to consume 70 percent of the time and effort of building a data warehouse. But there hasn't been enough careful thinking about just why the ETL system is so complex and resource intensive. Everyone understands the three letters: You get the data out of its original source location (E), you do something to it (T), and then you load it (L) into a final set of tables for the users to query. When asked about breaking down the three big steps, many designers say, "Well, that depends." The "it depends" response is dangerous because it becomes an excuse to roll your own ETL system, which in the worst-case scenario results in an undifferentiated spaghetti-mess of tables, modules, processes, scripts, triggers, alerts, and job schedules. The 38 Subsystems Extract system. More Insights

Traitements temporels en SQL - Cl La difficulté des calculs portant sur des dates ou des horaires (et parfois les deux) est lié à la codification même de la mesure du temps ainsi qu'au fait que le temps est une entropie (disons le, même une "isentroprie"), c'est à dire qu'il s'écoule de manière uniforme (iso) et dans un seul sens irréversible (vers le futur). La mesure du temps n'obéit pas à des règles conventionnelles, comme le comptage décimal ou l'origine zéro. En effet : Les années comptent tantôt 365 tantôt 366 jours en fait 365 jours 5 heures 48 min. 45,97 sec... Les mois de 29 à 31 jours Il n'y a pas d'année 0, mais il y a des années négatives (avant JC !) Tous ces éléments font que les calculs, notamment de comptage du temps obéissent à des algorithmes complexes. De ce fait, la norme SQL 2, propose une solution générale assez intelligente. NOTA : il est dommage que le calendrier mis en place lors de la révolution française n'ai pas subsisté. Le lundi est considéré comme le premier jour de la semaine. 1.1. 1.2.

Open source data quality, data profiling and master data management | DataCleaner Joda Time - Java date and time API - User Guide Architecture Overview The major building blocks of joda time are introduced below. These are the concepts of instant, interval, duration, period, chronology and timezones. We then say a few words about the role of interfaces in the library design, which is a little different than the norm. Instants The most frequently used concept in Joda-Time is that of the instant. Within Joda-Time an instant is represented by the ReadableInstant interface. The millisecond instant can be converted to any date time field using a Chronology. We discuss the chronology concept a litte further on in this overview. A companion mutable class to DateTime is MutableDateTime. Other implementations of ReadableInstant include Instant and DateMidnight. Fields The main API of DateTime has been kept small, limited to just get methods for each calendar field. Properties There is much more power available, however, through the use of what is termed a property. Intervals Durations instant + duration = instant Periods Chronology

Data Modeling & Profiling Tool: SQL Power Architect | SQL Power Software Features Accesses source databases via JDBC Connects to multiple source databases concurrently Compares data models & database structures and identifies discrepancies Drag-and-drop source tables & columns into the playpen Remembers the origin of each column Generates source-to-target visual Mapping Reports Forward/reverse engineers PostgreSQL, Oracle, MS SQL Server & more Saves source data structure snapshots in the project, so you can work remotely All project data is stored in an easy-to-parse XML format OLAP schema modeling: Cubes, Measures, Dimensions, Hierarchies & Levels Visual Mapping Report for data lineage tracking Free Download (Open Source, GPL v.3 licensed) (Community Edition) Data Architects, DBA's, Analysts and Designers rely on Data Modeling tools to facilitate and simplify their data Modeling efforts, while maximizing the use of their resources. SQL Power Architect can also open multiple source databases concurrently, even if they are from competing database vendors.

Date Dimensions Part 2 - SQL Server Central This is the second and last part of the date dimension series. In the first article we discussed how we can add the same dimension into the same cube several times as different names (role play dimension), the advantages and disadvantages of creating several named queries from the same date dimension table, the considerations around the unknown member in the date dimension, and the date hierarchies. In this article we will discuss: A date dimension that is used as a reference dimensionA date dimension that is generated and stored on the SSAS server (no physical table)Advantages and disadvantages of using smart date key e.g. YYYYMMDDEnabling users to select a date (or month) to be used in calculated measure using 'from date' and 'to date'Other topics about date dimension in SSAS 1. In Figure 1 below, Dim1 and Dim2 are normal dimensions, they are connected to the fact table directly. Figure 1. Figure 2. Option 1. Figure 3. So there are 2 advantages of using a reference dimension: Figure 4.

Related: