Problems importing SQL data

[David Nock]

On 11/3/04 10:53 AM, "Ruslan Zasukhin" <sunshine at public.kherson.ua> wrote:

> On 3/10/04 11:43 PM, "David Nock" <davidn at accessitsoftware.com> wrote:
> 
>>> Hi David,
>>> 
>>> 1) SQL LOAD DUMP not finished.
>>>   you only can self parse each next command (up to ;)
>>>   and send command by command.
>>> 
>>> viSQL utility can do this.
>>> but Hmm, you say this not works for you.
>>> 
>>> 2) if you have task import data from other DBMS, please look on
>>> Valentina_ODBC utility. You can import directly from DBMS via ODBC driver.
>>> Valentina Studio also can do this now.
>>> 
>>> 
>>> 3) I wonder you get 351 error on small db.
>>>   what cache size of Valentina you use?
>>>   use 8-10MB cache.
>>> 
>> 
>> Hi Ruslan,
>> 
>> 1) Have grabbed a copy of viSQL but doesn't seem to support server, only
>> local db.
> 
> Okay, Valentina Studio can work with both Local and Server dbs
> Even in the same time.
> 
>> 2) No ODBC driver available. :-( Guess I could always dump the SQL file into
>> MySql and then out through MyODBC. ;-)
>> 
>> 3) Is this the value passed to ValentinaInit() or the value in the
>> Server.ini file. They are 3Mb and 40Mb respectively.
> 
> ValentinaInit() -- affect only LOCAL SDK.
> .ini file affect Valentina Server itself.
> 
> So you run server with 40MB cache.
> 
> 
> --------
> David, I do not see clearly your task.
> What you need to do?
> By steps?
> 

Hi Ruslan,

Basically, we are looking at Valentina for an upcoming project and are
hoping to run some tests to see how well Valentina handles some of our
tasks. I was hoping to import some example data from an existing system and
then run some SQL queries against that data.

Cheers
Dave

**********************
David Nock
Senior Developer
Access-It Software Ltd
**********************