Your SlideShare is downloading. ×
0
Top 10 DB2 Support Nightmares #2
Top 10 DB2 Support Nightmares #2
Top 10 DB2 Support Nightmares #2
Top 10 DB2 Support Nightmares #2
Top 10 DB2 Support Nightmares #2
Top 10 DB2 Support Nightmares #2
Top 10 DB2 Support Nightmares #2
Top 10 DB2 Support Nightmares #2
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Top 10 DB2 Support Nightmares #2

535

Published on

The second instalment in our DB2 Support Nightmares series. Download if you dare! …

The second instalment in our DB2 Support Nightmares series. Download if you dare!
www.triton.co.uk

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
535
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Top 10 DB2 SupportTop 10 DB2 SupportTop 10 DB2 SupportTop 10 DB2 Support Nightmares & How toNightmares & How toNightmares & How toNightmares & How to Avoid ThemAvoid ThemAvoid ThemAvoid Them #2#2#2#2
  • 2. Part 2 – Are your tools up to the job? Image of a junior DBA Long elapsed times for BI queries (over 30 mins!) were causing one of our customers some serious headaches
  • 3. They tried……. Increasingtemp space Checking their BI tool Running DB2 Index Advisor Creating additional indexes IIIIIII IIIIIII IIIIIII IIIIIII
  • 4. So Triton stepped in….. We used one of our favourite analysis tools: Brother Eagle® From DBI Software
  • 5. …and we discovered A B C 1 2 3 4 A 1 A 2 A 3 A 4 B 1 B 2 B 3 B 4 C 1 C 2 C 3 C 4 Join A VERY high query execution cost SQL being generated by the BI tool was captured and found to be a Cartesian join of two tables Each with more than 25M rows! New indexes were not being used
  • 6. The Solution We reworked the BI report definitions to add missing database relationships The BI tool then generated correct JOIN predicates The reports were re-run to successful completion in under 2 minutes!
  • 7. The Moral of the Story Many applications (such as BI, ERP and Java frameworks) are generating their own SQL – it can be difficult to know exactly what’s getting thrown at DB2. Correct tooling (and the skills to interpret them!) is essential.
  • 8. www.triton.co.uk

×