hello again.

 

now i have another problem.

following your suggestion of using COPY INTO for the migration of my database from MSSql to MonetDB5, i indeed succeeded in copying some tables, enjoying very good performances (for example, one table with ~8 millions of records in ~13 seconds).

the new problem i'm facing now is that using COPY INTO for data with hebrew letters ends up with error.

 

i tried to supply COPY INTO a UNICODE enoded file, but than i have not succeeded in defining the tuple and record seperators.

 

the MonetDB5 itself is capable of storing and retrieving hebrew letters. i can tell this because i have no problem inserting such data through JDBC (actually, right now i have a java process working hard and slowly on copying such a table). so the problem is probably somewhere in the mclient application. is there any workaround for that?

 

thanks,

ewilde.