Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
from my experience I will use an OLE DB Connection with an OLE DB Provider from Oracle.
Is this also the best way for QlikView to connect to an Oracle DB.Or are there any advantages to use the ODBC Provider?
regards
Bastian
Hi Bastian,
From what I know, I also prefer OLEDB. I have experience that it is faster than ODBC, and the connection string with user/password stays within QV document, unlike in ODBC, you would have to create user/system DSN, which then anyone can use it. And, OLEDB is newer technology then ODBC.
I found someone's performance test result table:
Performance Comparison | |||||
---|---|---|---|---|---|
SQL | Access | ||||
OLEDB | DSN | OLEDB | DSN | ||
Connection Times: | 18 | 82 | Connection Times: | 62 | 99 |
Iterating through 1,000 Records Times: | 2900 | 5400 | Iterating through 1,000 Records Times: | 100 | 950 |
So I would say, if option for OLEDB is available go for it, otherwise ODBC does the work.
Hi Bastian,
From what I know, I also prefer OLEDB. I have experience that it is faster than ODBC, and the connection string with user/password stays within QV document, unlike in ODBC, you would have to create user/system DSN, which then anyone can use it. And, OLEDB is newer technology then ODBC.
I found someone's performance test result table:
Performance Comparison | |||||
---|---|---|---|---|---|
SQL | Access | ||||
OLEDB | DSN | OLEDB | DSN | ||
Connection Times: | 18 | 82 | Connection Times: | 62 | 99 |
Iterating through 1,000 Records Times: | 2900 | 5400 | Iterating through 1,000 Records Times: | 100 | 950 |
So I would say, if option for OLEDB is available go for it, otherwise ODBC does the work.
Hi.
Do you have examples of setting up the oledb and odbc connectiond documents ?
Want to connect to sql server for information.
Thanks
Ash
Hi Rakesh,
A question, we currently use an ODBC connection to Oracle, after an Oracle DB &driver upgrade we noticed that performance was poor. So then we tried OLE DB instead which was about 5 times faster then the ODBC was before upgrade.
The only reason we have not switched is due to some issues with number fields. when using OLE DB we get 2 trailing decimals.
We could of course declare all fields in the script but this would need a lot of extra developer work.
By any chance do you or anyone on this forum know how to fix this?
Maybe had a similar issue and found a feasable workaround
Kind Regards,
Alexander