Problems importing SQL data

[Ruslan Zasukhin]

On 3/10/04 11:12 PM, "David Nock" <davidn at accessitsoftware.com> wrote:

> I'm trying to import a file of data that has been exported in SQL format.
> 
> So far this is the result:
> 
> Executing SQL statements 1 by 1 works for a while then slow to a crawl
> i.e. 1 record/sec
> This eventually aborts after 19000 lines with a ', was expected' error. I
> copied out the offending record plus a few either side into a separate file
> and this file imports fine. This is also frustrating because it takes a few
> hours to get here.
> 
> Tried adding a flush every few records, but this causes an Error 351 after
> only a few records.
> 
> Tried importing via LoadDump (SQL), which reports that all imported fine
> after a very short time, but nothing has actually been imported.
> 
> Any have any thoughts on what to try next.
> 
> This is on Windows, a60, C++.

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.


-- 
Best regards,
Ruslan Zasukhin      [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list go to:
http://lists.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------