Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
difference between oledb and odbc in qlikview
it does not matter what you use
Hi
i attached some interesting link and a image to undestand the difference
Differences between OLE DB provider and ODBC data source connections - Excel - Office.com
oledb - what is the difference between OLE DB and ODBC data sources? - Stack Overflow
* If the user wants to access data independent of the SQL language , you should migrate to OLE DB . As noted , the connectors are linked to ODBC SQL language.
* If the user's problem can solve directly manipulating tables , it is best to use OLE DB .
* If the user wishes to multidimensional data parallel interfaces , OLE DB is recommended as it is the only standard for data and models with these characteristics, and reduces the required amount of code and execution time.
* If the user requires access to different databases (local, shared , IOM, etc. ) from a single application , use OLE DB , otherwise you will be using separate routes for each access method code. This is also based on the idea that the OLE DB connectors reduce the differences between drivers , SQL and DBMS dialects have been problems between the ODBC settings.
* If the user need is to run concurrent updates , the OLE DB architecture is the best choice . To update records using an ODBC driver , the user must generate SQL UPDATE statements that are basically oriented batch updates . There is no concept of records in an ODBC block model.
The OLE DB architecture accommodates various models allowing the management of data from many more applications.
It is for this that QlikView for developing complex models that depend on multiple databases , you should use OLE DB connections instead of ODBC connections.
Good luck
Fernando
Microsoft designed the OLEDB API.
Microsoft's release of SQL Server 2012 is the last to include an OLE DB provider for SQL Server.
Microsoft is aligning with ODBC (2011) for relational data
Microsoft created OLEDB but now encourages to adopt ODBC