In the first part of this series I said that RAM access is the slow component of a modern in-memory database engine and for performance you’d want to reduce RAM access as much as possible. Reduced memory traffic thanks to the new columnar data formats is the most important enabler for the awesome In-Memory processing performance and SIMD is just icing on the cake.
This is the text of the “whitepaper” I submitted to DOAG for my presentation on “Core Strategies for Troubleshooting”.
In an ideal world, everyone who had to handle performance problems would have access to ASH and the AWR through a graphic interface – but even with these tools you still have to pick the right approach, recognise the correct targets, and acquire information at the boundary that tells you why you have a performance problem and the ways in which you should be addressing it.
Bush Sr. was president. The phone kept ringing off the hook after I faxed my resume to the telephone numbers in the want ads on the back pages of Computerworld. The nice people on the phone asked me “how comfortable would I be programming with C”. I could not lie so I replied that “I would be very comfortable programming with C.” That was the only question they asked me, other than “when could I start?”(read more)
Squarespace is a drag-and-drop website-builder for small organizations and creative professionals wanting a polished and functional web presence. Squarespace sites are quick to create and then “just work” without any worries over ongoing maintenance or version updates.
The web is replete with stale websites that are all but abandoned after the initial build. The common scenario I see is of a site developed in a rush of enthusiasm by someone having just enough technical knowledge to stand up a web presence on a platform like WordPress or GetSimple. Perhaps a volunteer burns the midnight oil for a few weeks. Such effort cannot be sustained. Updates bottleneck on the one person who can make them. In short order, the site goes stale.
The last added function was the cmp function, which we needed to finish the overall goal, of the package: To create a "satisfies" function, that can verify if a specific version is satisfied within a range of versions.
The different ranges, that can be specified are X-ranges (Wildcard, i.e. 1.2.* or 2.*), Tilde-ranges (minimum requirements for minor versions, ~1.2.3, which will allow versions between 1.2.3 and up to 1.2.n, but not 1.3.0) and Caret-ranges and Hyphen ranges. For a full description and detailed example, you should read the following 2 articles:
It’s gettting to that time of year, so here are some of the sessions I’ve pencilled in for UKOUG Tech 15:
Probably the whole of the Development stream.
9:00 – 9:50: Tom Dale – Fivium : An insight into Oracle Standard Edition, what’s included, what’s not, and how to plug some of those holes!
11:20 – 12:10: Me (et. al.) : Cost Based Optimizer – Panel Session
12:20 – 13:10: Franck Pachot – DBi Services : All About Table Locks: DML, DDL, Foreign Key, Online Operations,…
14:10 – 15:00: Maria Colgan – Oracle : Oracle Database In-Memory By Example
15:10 – 16:00: Philip Brown – Red Stack Tech : How to Evaulate the 12c In-Memory Option
16:30 – 17:20: Tony Hasler – Anvil Computer Services : Optimizer Roundtable
17:30 – 18:20: Joel Goodman – Oracle : Oracle Standard Edition Roundtable
Technical people tend not to enjoy Keynotes at conferences. We are allergic to content-light “there has never been a better time to invest in our products” fluffy, frou-frou, big picture talks. We want how-it-works meat on the bones of what is served up to us.
Another annual DOAG conference has passed, and I can only say the very best about it: Perfectly organized, large and modern location, impressive list of well known speakers and over 2100 attendees – wow!
My presentation Best of RMAN was scheduled at the first slot on the first day, so I was a bit concerned whether many people would attend that early. It turned out that the room got so full that I was asked by the organizers to deliver the same talk again next day – which I happily did, again with a packed room :-)
You need to be careful when coding and using triggers when it comes to Datapump (or anything that transposes triggers between schemas). A lot of people make assumptions about what will happen with their triggers, and often get a nasty shock when they see the reality. Lets explore with an example
I’m going to add three triggers to the standard EMP table in the SCOTT schema