Advice on Finding Your Way Around a New Oracle Database

thatjeffsmith SQL Developer 2 Comments

Received this query from a customer this morning… For your information, I’m average in SQL. What I would really like to know is if you can give me some tips regarding the use of Oracle SQL Developer in relation to a completely new database. So, are there functions/tools in Oracle SQL Developer which can help me better understand a new …

Modeling Virtual Columns

thatjeffsmith SQL Developer 4 Comments

Virtual columns made their debut in Oracle Database 11g. They are a value that’s not stored with the row, rather they are computed as queried. [DOCS] So I could have a column of type DATE. And I could have a virtual column of type VARCHAR2 that is computed by running a function against the previously mentioned DATE column. How would …

Discovering Foreign Keys in Oracle SQL Developer Data Modeler

thatjeffsmith SQL Developer 4 Comments

Columbus didn’t exactly discover America. And we’re not really going to discover your long, lost foreign keys. But, we’ll do our best to guess where they might be. Our data modeling tool is often the bearer of bad news – your database doesn’t actually have any referential integrity defined. Oh, it’s defined somewhere, in the application. Probably. Just not in …

12c Temporal Validity Support in SQL Developer Data Modeler

thatjeffsmith SQL Developer 0 Comments

Today’s question: can I design a table that takes advantage of the new Temporal Validity feature in Oracle Database 12c? Today’s answer: ‘Yes.’ In a nutshell: Temporal Validity Support lets you associate one or more valid time dimensions with a table and have data be visible depending on its time-based validity, as determined by the start and end dates or …

SQL Developer Data Modeler, Pending Changes & Versioning

thatjeffsmith SQL Developer 9 Comments

Oracle SQL Developer Data Modeler supports the one-gal design boutique shoppe and the mega-huge development team. It HAS a file-based repository (Subversion aka SVN.) You don’t have to use it, but you should. You can optionally store your designs and data dictionaries in a database for reporting purposes. I strongly recommend you do so. If you do add your design …