My bike is monitored by Exadata…

By -

I am a big fan of Garmin's sports gadgets and at the moment I have a Forerunner 210 on my mountain bike, a 310XT watch on my Trek 5200 and an Edge 705 loaded up with a map for my area of northern England on my Trek 5900SSL. Every morning I am either out on one of my road bikes if it is not raining or running with my 310XT watch if the weather is not so good. At the end of the week I connect both my Garmin devices to my computer and upload all the data I have collected to the Garmin Connect website so I can check on all the usual training statistics.  Turns out that I am actually using Exadata every single day! Garmin runs their Connect web application, along with its data warehouse and other operational systems, on Exadata. 

Here is a great video that really gets to the heart of why you want Exadata in your data centre and if you are Garmin user you will be pleased to know that every time you turn on your Garmin device you are actually using Exadata. 

(If the video above is not visible or does not play then you can view the try following this link to the post on YouTube: http://www.youtube.com/watch?v=jjB6mKYOr7M)

 Now, when I get up in the morning and press the power button on my Garmin device that startup process is going to be just a little bit more special. Great to know that Garmin and Oracle have got me covered, logging everything heart beat, calorie, pedal revolution, wattage and mile that I do each and every day. If you have never seen Garmin Connect then visit the website where you can take a guided tour of the features and check out all the latest Connect-enabled devices: http://connect.garmin.com/

Comments

Post a Comment

Popular posts from this blog

My query just got faster - brief introduction to 12.2 in-memory cursor duration temp tables

By -
Image
Image courtesy of wikipedia This post covers one of the new SQL performance enhancements that we incorporated into Database 12c Release 2 . All of these enhancements are completely automatic, i.e. transparent to the calling app/developer code/query. These features are enabled by default because who doesn’t want their queries running faster with zero code changes? So in this post I am going to focus on the new In-Memory “cursor duration” temporary table  feature. Let’s start by looking at cursor duration temp tables… Above image courtesy of wikimedia.org What is a cursor duration temp table? This is a feature that has been around for quite a long time. Cursor duration temporary tables (CDTs) are used to materialize intermediate results of a query to improve performance or to support complex multi step query execution. The following types of queries commonly use cursor duration temp tables: WITH Clause and parallel recursive WITH Grouping Sets S...
Keep reading

SQL Pattern Matching Deep Dive - Part 1

By -
Image
There has been quite a lot of interest in the new 12c MATCH_RECOGNIZE feature for SQL pattern matching. Therefore, I thought now would be the perfect time to start a series of quick deep dive posts that explain how SQL pattern matching works. Over the coming weeks I will cover the following topics in a series of posts. This is the start of a series of posts based on a presentation that I put together for the recent annual  BIWA conferenc e at Oracle HQ. The Oracle BI, DW and Analytics user community always puts on a great conference and this year was the best yet. You can download any or all of the presentations from this year’s conference by following this link . My pattern matching deep dive presentation started life about a year ago as a post covering some of the new keywords in the explain plan that are linked to pattern matching, see here . It has now expanded to cover a much wider range of topics. Firstly, a huge vote of thanks to my development team (Lei Sheng and Chun-Chie...
Keep reading

SQL Pattern Matching Deep Dive - Part 6, state machines

By -
Image
The obvious way to start this particular post is to pose a couple of simple questions: what is a state machine and why should you care? In general I would say that you don't need to know about or care about state machines. That's the beauty of using SQL for pattern matching. The MATCH_RECOGNIZE clause encapsulates all the deep technical modelling and processing that has to be performed to run pattern matching on a data set. However, there are times when it is useful, probably vital, that you understand what is going on behind the scenes and one of the most obvious situations is when backtracking happens. Therefore, the content covered in this post is a going to be a gently lead-in into my next post where I am going to discuss the concept of “backtracking”  and the dreaded  ORA-30009 error. Let’s start our voyage of discovery…when you attempt to run a SQL statement containing a MATCH_RECOGNIZE clause during the compilation phase we generate a finite state machine ba...
Keep reading