![odbc excel odbc excel](https://alt2.minisoft.com/support/wp-content/uploads/2014/12/ODBCac01.gif)
I need to tell my Windows what is my driver name and what is its path and so on. Registry KeyĪnd the last part is registry keys. A good place for some optimisation in my opinion. Every locale is about 1.5 megabytes and has 48 files. But there are 29 locales and I think most of the time you will need only one or two of them. Again if you agree with not the smallest client in the world, you may take the whole locale. C:\BI-client\bi\bifoundation\server\locale, for example. The second folder you need is locale, it is located near bin. You won't win the smallest ODBC client contest but will save a few minutes of your time. C:\BI-client\bi\bifoundation\server\bin for example. These libraries should go under bin folder. The list has only 25 libraries but it takes too much place on the screen so I put them into a collapsible list in order to keep this post not too long. I tried to find the minimum viable set of the libraries. C:\BI-client\bi\bifoundation\server for example. It should be something\bi\bifoundation\server. So we can't put DLLs to any folder we like. So that was a short story of looking and finding things.
![odbc excel odbc excel](https://www.eonesolutions.com/wp-content/uploads/2016/06/062416_1351_Troubleshoo1.png)
#ODBC EXCEL FULL#
Compare it to 31 thousand files of the full client. With only English locale it has a size about 20 megabytes and consists of 75 files. So, as a result, we got a tiny ODBC-related OBIEE client. Just give it a DLL to explore and it will show all DLLs used by it and mark all missing.Īnd a bit of educated guess helped to find one more folder called locale which stores all language files.
![odbc excel odbc excel](http://www.thesqlreport.com/wp-content/uploads/2016/03/07_ExcelSetupConnection.jpg)
This tool is very easy to use and very useful for finding a missing DLL.
#ODBC EXCEL FREE#
A small free utility Dependency walker helped me to find out a set of DLLs I need. So now I know names of the DLLs and their places. I deleted some keys in order to make this screenshots more clear and readable. Anyone who has ever tried to play around Windows ODBC won't be surprised with it at all. OBIEE installer doesn't copy a single byte to the Windows folder (and it's a good news I think) but it creates a few registry keys (what was expected). Does it copy something to the Windows folder or everything stays in its installation folder? Does it make any registry changes (apparently it does but what exactly)?įor this task, I took a fresh Windows, created a dump of the registry and folders structure of the Windows folder, then installed OBIEE client using normal installation process, made the same dumps and compared them once again. The first thing I needed to know what changes Oracle's installer does during an installation. But anyways the main points will be highlighted. It's less a detective thriller and more a tedious story. I will not describe in full details the process of the investigation as it is not too challenging. It’s not a supported functionality or Oracle’s recommendation. Everything below is a result of our investigation. I need a small "thing" I can easily copy to any computer and then use it.ĭisclaimer. And the second aim was avoiding a full installation with cutting out redundant pieces. So what I had in mind with this research was to make a set of OBIEE ODBC libraries as small as possible. Even if our security won’t let them break anything, why would we stuff his head with unnecessary things? Let's keep things simple. We don’t want to give a full set of developer tools to an end-user. Not a huge problem considering HDD sizes and prices but something not so good if you have an average-sized SSD.Īnd the second point to consider. Full (and the only possible actually) client OBIEE installation is more than 2 gigabytes and consists of more than 31 thousand files. But there is a little problem with the OBIEE 12c client installation - its size. But a lesser-known benefit of this is that we can utilise this ODBC interface for own needs. The OBIEE BI Server (nqsserver / OBIS) exposes an ODBC interface (look here if you live in a world full of Java and JDBC) which is used by Presentation Services and Administration tool. Without exports or plugins! Querying OBIEE Directly from Excel? With No Plugins? What Is Going On! I'm sure you've recognised the most favourite data analysis tool of all times - Excel.īut what you can't see in this picture is the data source for the table and charts.