Did you know that you can call Spotlight on DB2 LUW from Toad for DB2 LUW and vice versa? Well, ok maybe you did. If that’s the case, please move along, there’s nothing to see here. Still with me? Then read on!

Toad for DB2 LUW and Spotlight on DB2 LUW exist as separate executables on your workstation. You might now be thinking “no kidding, Ben.” That’s fine. After all, I have been called the Master of the Obvious. However, we may find ourselves working in one solution and then realize we have the need to work in the other solution. Naturally, we can just launch the solution of interest from our programs menu. However, let’s consider saving ourselves a little bit of time and launching them within some proper context. Let’s say I’m working in Toad for DB2 and have the need to do additional diagnostics using Spotlight. Rather than launching Spotlight, selecting the proper database connection and then connecting, I can simply use the Tools -> Quest Tools -> Spotlight on DB2… menu within Toad:

Spotlight on DB2 LUW then loads and creates a new Spotlight connection using the connection’s information from Toad for DB2!

Let’s consider the opposite approach. I may be diagnosing an issue in Spotlight on DB2 LUW and realize that I need to perform an operation within Toad. In this example, I’m working in the Tablespace Analysis drilldown in Spotlight. If I right-mouse click on a tablespace, a window loads that allows me to operate on the object using Toad:

If I choose the Alter… option, Toad for DB2 loads, connects to the database I was diagnosing in Spotlight, and then loads the appropriate menu for Altering this tablespace:

I encourage you to use the solutions in a manner that is most comfortable to you. With the integration that exists between Spotlight on DB2 LUW and Toad for DB2 LUW, I can save myself time and use these solutions within a relevant context. Just a little something else to think about!