Due to scheduling conflict though, it’s on a Thursday evening for once! I will be presenting for the first time as an Enkitec employee in Colorado Springs, March 22nd. All you SQL Server folks out there that want to come on out, here are the details: SpringsSQLRead More SQL Saturday Presentation!
I’ve been again, unfortunately, reminded what makes a poor work environment for a DBA or Developer. Eddie Awad had sent this out and the second one really resonated with me: http://www.washingtonpost.com/national/on-leadership/how-to-completely-utterly-destroy-an-employees-work-life/2012/03/05/gIQAxU3iuR_story.html?tid=sm_twitter_washingtonpost I refer to this in the IT world as the “technical bully syndrome” and it’s quite common in the arena. It’s not because it’s […]Read More The Technical Bully Scenario
Kellyn’s Schedule of Presentations, 2012, 2nd and 3rd Quarter March 24th, 2012, Colorado Springs, CO SQL Saturday Oracle for SQL Server DBA’s April 19th, 2012, Billund, Denmark MOW 2012 ASH Analytics- Top Activity, the Next Generation April 20th, 2012, Billund, Denmark MOW 2012 EM12c: Making Oracle Enterprise Manager Work for You May 30th, 2012, Hämeenlinna, […]Read More Kellyn’s Presentation Schedule, Spring/Summer 2012
Yes, my dear Watson, Bind Peeking is still an issue in 11g…. We recently upgraded from 10.2.0.4 to 220.127.116.11.0 and come across a couple interesting performance challenges. I do like this type of problem and have been quite busy working on the fixes for each one that has shown itself. This was one of the […]Read More 11g, Sherlock Holming it with Statistics, Histograms and Bind Peeking
As part of an 11g Upgrade, it was found that a database environment could be built from one of the upgraded databases through a duplicate. As this process had never been performed before in this fashion, a test was in order. The test was an excellent chance to discover that the OSUser that performs the […]Read More Restarting a Duplicate Process From a VERY Failed State
I had worked hard on a report, 47 SQL statements in all to tune it down from 5 hrs to under 30 minutes. The first runs had been quite successful, so when a third run sent an alert on temp usage, I knew something was wrong. SID PROCESS MACHINE SQL_TEXT SQL_ID TOTAL MB ——– ———— […]Read More The NO_INVALIDATE Option in DBMS_STATS with 10g