Oracle OpenWorld Experiences- Part 1



  • “I LOVE Toad!”
  • “Toad rocks!”
  • “I couldn’t live/do my job without it.”
  • “I am where I am today because of Toad.”
  • “Toad?  Absolutely essential in our org.”
  • “Toad if the first thing I bring up in the morning, and the last thing I close before heading home.”
  • “I told my manager ‘The day you take my Toad away is the day you’ll see my resignation e-mail in your inbox.’ ”
  • “Whenever I switch jobs, I tell the new boss that Toad is part of my hiring requirement.”
  • “I’ve brought in Toad at each company I’ve ever worked.”

I’ve heard every single one of these remarks—and some of them many times!—at this year’s Oracle OpenWorld show, and at recent customer onsites in the last few months.   OK, I work for the company that develops Toad solutions.  So naturally I get pumped when I hear such glow about our Toad products.


The WHY.

But the above comments allude only to the “what”—the “what” being Toad in this case.   So imagine how much more excited customers can get when they add the WHY to their WHAT.   Here’s a few more quotes from OpenWorld and customers:

  • “Toad makes me look awesome.”
  •  “Compared to what I used to do by hand, Toad saves me at least an hour every day.”
  • “Toad does all of our schema changes and syncs, code reviews, performance tuning, data fixes and data validation in a tenth of the time it took using conventional methods.”
  • “Our dev teams work twice as fast with Toad.”

These statements provide insight as to WHY the WHAT is highly valued.  Toad is a valued product because it was crafted from Day One to increase productivity and promote quality database change with less risk.  And for almost all customers, this equates to dollar savings.  Sometimes BIG dollar savings.


The HOW.

Ah, but when customers tell me HOW they do the WHY with the WHAT, oh, that’s where it gets REALLY beautiful!   I started a blog series in one of our Quest Communities a while ago on this very topic.   The series is entitled “Toad Turnpike: Real Stories from the Road”, and I’m continuing it here, in Toad World.  Of the millions of Toad users—yes, millions of paying customers across the globe!—some of these customers use Toad in creative ways to accomplish things that simply make a difference.   Some of those differences might be small, but some are big, some important, some strategic.

 Like the lady who used Toad to save her company over $40,000 hard cash.  No kidding.  That statement says Toad, the WHAT, is awesome in a big way.   And the $40,000 WHY part of that statement can’t be argued with.  But if you’re intrigued as to HOW Toad did it for her, read here.  Or how about this development lead who could have saved two man-days of investigative effort on a troubling issue?   If only he had known HOW Toad’s Code RoadMap feature could have minimized time to resolution, he could have minimized the time his rear-end was in the hot seat, and prevented proverbial third-degree burns on his backside!

I know that you’ll be encouraged by these stories and others like them.  I’m hoping they will encourage you enough to do some “off-roading” of your own in Toad, and make a difference in your company.


A Cliff Hanger.

So, time for another real story from the Toad Turnpike.  An IT Director comes up to me in our Quest booth at OpenWorld last month.   The gentleman doesn’t have a lot of time, gets right to the point and asks:  “Our CEO mandated cost-cutting measures this year, and our teams are supposed to adopt the free native tools from our database vendors.  But some of my team members are threatening to quit if Toad is taken away.  Tell me how to convince my superiors that we’re pulling rank and need to continue paying for Toad.”

He’s asking for justification.  My first thought is, “Whoa, losing some of your highly-valued people isn’t reason enough!?”   OK, I’m not saying that out loud.  My second thought is that he should get the reasons directly from his team members.   I’m not saying that either.  Then, wow, how do you answer such a question?   I think about this for a few moments, and several customer stories come to mind.  I choose to tell the account of a Mortgage Lending customer who had a project to automate most of their QA department’s processes.  Bottom line?  Toad helped to complete the project two months AHEAD of schedule!  That kind of example would be justification for many folks.  However, the Director’s cell phone rang just as I was about to explain HOW Toad made this happen, and he had to step away.   I didn’t see him for the rest of the show. 

Well, I don’t like to leave people hanging, even if it’s not my fault.  So, for this IT Director, wherever you are—and for others who want to hear the happy ending to my cliff-hanger—I’ll let you guess at the HOW part of the story until I post the details in the next blog. 

HINT:  If you’re already guessing that Toad’s workflow automation engine is the answer, you’ll get bonus points from me for even knowing that Toad tasks can be automated, congratulations.  But Toad’s automation capabilities played only a small part of the solution.   The HOW in this case involved a feature that few Toad users know about, even though it’s been in the product for years.  Stay tuned! 


The real-world story continues.  Please visit Part 2  for the interesting conclusion.


About the Author

Gary Jerep

As a Software Consultant within Quest, Gary Jerep has over 20 years of experience assisting DBAs, Developers and Analysts with relational database needs. Prior experience includes systems design and analysis, operations research, Business Intelligence, and end-user experience monitoring.

Start the discussion at