Skip to Content
avatar image
Former Member

dbisql command line options

Hi all,

I've just added a HANA client to my computer and came across a few details when trying to connect to HANA using interactive SQL.

1. (this is not precisely HANA related, but came to my attention in this context) There are command line options to advise dbisql to connect to a HANA (-hana), IQ (-iq) or UltraLite (-ul) database, but I didn't find any for SQL Anywhere or Generic ODBC. When starting dbisql without parameters, the connect dialog box is preset with the database type I had picked the last time. I think additional options for these two types would be systematic.

2. When connecting to HANA using an ODBC data source, the ODBC style connection parameters UID and PWD are not recognized. "user" and "password" are expected instead.

dbisql -hana -c "dsn=VolkerOnMonsoon;uid=Volker;pwd=Ger0nimo" doesn't recognize the userid / user name and prompts for missing connection parameters.

dbisql -c "dsn=VolkerOnMonsoon;uid=Volker;pwd=Ger0nimo" works, but gets me a generic ODBC connection.

dbisql -hana -c "dsn=VolkerOnMonsoon;user=Volker;password=Ger0nimo" works and gets me a qualified HANA connection.

dbisql -datasource VolkerOnMonsoon -c "user=Volker;password=Ger0nimo" dto.

dbisql -datasource VolkerOnMonsoon -c "uid=Volker;pwd=Ger0nimo" brings me to a SAP HANA connect dialog without user name or password preset.

(of course Ger0nimo is not the real password)

What I would consider consistent: At least when connecting using an ODBC data source name, ODBC connection parameters should be recognized, regardless of database type. If dbisql recognizes that the data source is one of the explicitly supported systems, all the better.

What do you think about my ideas?

Thanks & regards

Volker

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Apr 13, 2015 at 09:20 PM

    Hi Volker,

    1. I've opened CR #782623 to address this point. This behaviour has also affected me when I was doing my HANA testing - you can't connect to a SQL Anywhere database if you have manually changed the database type. I agree, this is not convenient at all... 😊

    2. We are aware of the discrepancy in the HANA connection options. I had made an attempt to document some of these settings on the "Starting Interactive SQL" page a while ago: DocCommentXchange. Adding a DSN to the mix really just complicates the problem further - is this a major issue for you?

    Regards,

    Jeff Albion

    SAP Active Global Support

    Add comment
    10|10000 characters needed characters exceeded