Hello,
We are having a performance issue when running queries via an ODBC connection. When we run the queries in vsql they perform ok. Any idea why this may be happening?
Thanx!
Queries made with ODBC are really slow...
Moderator: NorbertKrupa
- JimKnicely
- Site Admin
- Posts: 1825
- Joined: Sat Jan 21, 2012 4:58 am
- Contact:
Re: Queries made with ODBC are really slow...
Hi there,
Make sure your ODBC connection's transaction isolation level is the same as your Vertica database server. The default isolation level for an ODBC connection is "Serializable" whereas the default isolation level for the Vertica database is "Read Committed". Try changing your ODBC setting to match the database (if they're not already the same).
For Windows you'll need to go to the ODBC Data Source Administrator. Make sure the "Read Committed" radio button is selected. (Depending on your Windows/driver version, this field may be a drop down).
Here is an example DSN entry from my odbc.ini file:
Make sure your ODBC connection's transaction isolation level is the same as your Vertica database server. The default isolation level for an ODBC connection is "Serializable" whereas the default isolation level for the Vertica database is "Read Committed". Try changing your ODBC setting to match the database (if they're not already the same).
For Windows you'll need to go to the ODBC Data Source Administrator. Make sure the "Read Committed" radio button is selected. (Depending on your Windows/driver version, this field may be a drop down).
Here is an example DSN entry from my odbc.ini file:
Code: Select all
[vertica_prod01]
Driver = Vertica01
Servername = 10.255.100.37
Database = vertica_prd01
Port = 5433
UserName = cognos
Password = thisisnotthepassword
TxnReadCommitted = 1
ConnSettings = SET SEARCH_PATH TO "$user", cognos, public, v_catalog, v_monitor, v_internal
Jim Knicely
Note: I work for Vertica. My views, opinions, and thoughts expressed here do not represent those of my employer.
Note: I work for Vertica. My views, opinions, and thoughts expressed here do not represent those of my employer.