Use of JDBC Trace feature

Question

I want to see what SQL statements are executed against HANA when I run BObj Analysis for Excel on top of HANA views I had created. Accordingly to the HANA Development Guide p.63 it should be possible. Actually, I don't see my SQL statements in the log.
Details are as follows:
1. I have enabled JDBC Trace in HANA Studio, in properties of the HANA db instance I'm working with. Well, the Guide advises to use a separate NGDBC.JAR for it, but I assumed that would be the same functionality. Q1: Is there any difference in terms of JDBC Trace contents, depending on the way it's been enabled with?
2. I have an analytic view MYCONTENT.ANV_001 that has, say, attributes SHIPTO and CALMONTH and a measure SALES. When I open the view in BObj Analysis for Excel, I expect it to run a SQL statement like SELECT SALES FROM MYCONTENT.ANV_001
3. Yet I don't see anything like that. The only SQL statement that may be related is "select * from DUMMY".
4. I tried to navigate through the view in Analysis for Excel, e.g. do some drilldowns and filters, but it continued running the same SQL statement against HANA.
Q2: Have I picked the executed SQL statement right? If yes, does it mean that BObj Analysis for Excel always generates most generic query against HANA? If no, how can I check what is the SQL statement being executed?
Update 5. I tried to enable JDBC Trace using the NGDBC.JAR library, but see no trace logs appearing at all. Q3: Could it be something wrong with the trace settings (well, there are just 4 of them, and it would be hard to make a mistake)? Q4: Does Analysis for Excel use JDBC Driver at all to access HANA?
Thanks!
/RB
Edited by: Roman Bukarev on Dec 13, 2011 4:53 AM
Edited by: Roman Bukarev on Dec 13, 2011 4:54 AM

Answer 1

I second that. Using JFrame instead of JApplet is easy once you've seen an example:
http://java.sun.com/docs/books/tutorial/uiswing/learn/example1.html
When learning Swing, I can think of only disadvantages to using JApplet over
JFrame. Why do textbooks use applets? Old habits die hard and they
are out-of-date in their view of Java.
Side comment: when learning a new topic, like JDBC, I would
strongly advice you to write the simplest possible code at first.
In other words, skip the Swing and write simple console apps:
1. select and dump the contents of a table.
2. gradually do more sophisticated selects...
3. insert a record into a table using some fixed values.
3. delete records from a table.
4. update records using some fixed values.
Once you are comfortable doing CRUD, and used PreparedStatement!,
then add a GUI. And if your code is well-written, the GUI and the back-end
are separate enough anyway, that you can write and test them apart.