Hi,

How can I execute large SQL files (100 MB size). ISQL is not even able
to handle files of 10 MB! I cannot delete the SQL History anymore, ISQL
and Central crash!

Any help would be greatly appreciated!

Tom

Did you try: dbisqlc read commandfile?

Arthur
--



at wrote:

What version are you using?

Are you trying to use dbisql in the GUI mode? If so, why? ...do you
expect to edit a 100MB file using keyboard and mouse? Just asking...

Have you tried running dbisql in batch mode? i.e., put the filespec on
the command line to just process it in non-GUI mode. I do not know if
that will work, but it might be worth trying.

What is in the file? If it is INSERT statements, consider switching to
using an INPUT statement, or better yet, a LOAD TABLE.

To fix the History crashing, you might be able to delete one or more
of the "configuration" files that dbisql and scjview create. Where
these files are, and what their names are, depends on the version.

Breck




On 20 Dec 2009 00:46:59 -0800, at <"pub (at) bednarz.ch"> wrote:

--
Breck Carter - Blog: http://sqlanywhere.blogspot.com/

SQLA questions and answers: http://sqla.stackexchange.com

RisingRoad helps SQL Anywhere developers make better databases
http://www.risingroad.com/
Breck.Carter at gmail

In article <ffnui59ci4doal749i5g9a3la6c5ddi3m2 (AT) 4ax (DOT) com>,
NOSPAM__breck.carter (AT) gmail (DOT) com says...
I imagine isql may have trouble with that large of files, but I
routinely handle 200+ MB text files with UlstrEdit, and have handled
over 1GB with no trouble.

D

Thank you all for your replies.

I use SQLAny 11.0.1 2299

It is not an editor problem. I had a programming error and needed to
translate lots of transaction logs in sql. Then delete the erronous
transactions and then replay them. It is a bit hard with a 2.5 GB SQL
file!!

ISQL and Central do crash for every bloody file bigger than 5 MB!

Tom

David Kerber schrieb:

2.5 GB SQL statements from the translation log?
Well, *that* wouldn't fit in my brain's memory, either

Have you tried to use isql/dbisqlc in the "no-gui" mode as recommended?
If so, has it helped?

Just to let others know...


Volker

at wrote:

Tom,

If it is not clear, the feature of dbisql that can handle this
is the READ command. When you provide the .SQL file
on the dbisql cmdline it is the same thing as an implied
READ command.

The READ statement
"run[s] a command file without loading it into the SQL Statements pane "
http://dcx.sybase.com/1101en/dbusage...s-4696303.html
effectively executing small blocks of SQL (down to single statements
in your case ... but generally depending upon the file contents) at a time
and requiring much less memory and little overhead.

The READ statement has always been present in all versions of
DBISQL (going back to at least 5.0 and probably before).

http://dcx.sybase.com/1101en/dbrefer...statement.html


"Volker Barth" <No_VBarth (AT) Spam_GLOBAL-FINANZ (DOT) de> wrote