Hello Forum,
I’m dealing with a report where a SELECT is driving up CPU. How do you usually approach profiling COBOL + DB2 queries—EXPLAIN, RUNSTATS, index review? What’s your go-to order of attack? Appreciate any ideas or examples.
DB2 batch SELECT taking too long
-
Aakash Kochar
- New Member
- Posts: 4
- Joined: Mon Aug 04, 2014 2:31 pm
Create an account or sign in to join the discussion
You need to be a member in order to post a reply
Create an account
Not a member? register to join our community
Members can start their own topics & subscribe to topics
It’s free and only takes a minute