Hi Sjoerd - Thanks for responding so quickly. On 13 Oct 2008, at 13:48, Sjoerd Mullender wrote:
The ODBC driver can produce a log if you start the process that loads the driver with an environment variable ODBCDEBUG with as value the file you would like to use to collect the log (i.e. something like set ODBCDEBUG=c:\odbc.log )
Thanks, I'll try that. Is there any way to set it without an environment variable (e.g. an ODBC manager setting or a connect string attribute?) That would allow me to separate logging MonetDB data from the logs generated by the data source used for import. Although we have found that we can't seem to load a different ODBC driver at the same time.
What kind of system are you using? 32 bit or 64 bit? XP? Vista?
32 bit XP, but we want to be able to work on all of these.
If a 32 bit system, remember that all data has to be addressable (i.e. less than 2GB), and this includes all temporary tables that are used while loading. (The database can be bigger, but all data that is referred to (used) in a query has to be addressable at the same time.)
So this places a limit on the size of a database that can be accessed on a 32 bit machine? Or is it simply an insert limitation? Let me back up a bit. We are investigating using MonetDB for OLAP in a desktop product. We have no restrictions (currently) on the size of the database the user can analyse. Most users are running 32 bit XP. Can MonetDB handle databases larger than 2Gb on such a system?
Conversions happen because the interface to the server uses UTF-8 and often the interface from the application to the driver (actually, the interface between the driver manager and the driver) uses wide characters (i.e. UTF-16). But I would be interested in fixing any bugs in that area, so if you can capture a log session where it goes wrong, I'd be grateful.
I'll try to get some output for you. ________________________________________________________ Richard Wesley Senior Software Developer Tableau Software Visit: http://www.trytableau.com/now.html