Hi Tim,

Remember how you fixed that progressive slow-down in ADO.NET when migrating
a database, using nothing but your immense intellect and unrivalled coding
skills (I'm hoping flattery might help my cause!

.... well I'm coming across a similar problem when running through a create
database script (which is basically a long list of CREATE TABLE commands).

At first I was executing the whole script in one
EDBCommand.ExecuteNonQuery() call.

There were two problems with this :-

[1] Progressive slow-down when running the big script
[2] The OnProgressEvent doesn't fire consistently at all (it seems to sit at
0% for ages and then shoot up to 100% in the last few seconds).

So I am now splitting up the script into individual SQL statements which I
execute one-at-a-time. I hoped this solution would fix both problems but
oddly, while it has solved the progress bar issue, I am still experiencing
progressive slow down - even though I am executing each command one at a
time.

Here's a small project which clearly demonstrates the problem :-
http://files.pioneersoftware.co.uk/temp/ElevateDB_Test.7z

Look forward to your thoughts!

Hedley,

<< ... well I'm coming across a similar problem when running through a
create database script (which is basically a long list of CREATE TABLE
commands). >>

It should be similar - it's the same issue.   The issue is with the
config/catalog writing performance, so any continuous set of DDL statements
will experience the same problem.

<< [1] Progressive slow-down when running the big script >>

Same issue again.

<< [2] The OnProgressEvent doesn't fire consistently at all (it seems to sit
at 0% for ages and then shoot up to 100% in the last few seconds). >>

Scripts rely on you using SET PROGRESS TO statements to indicate progress to
the user.   Any normal progress updates that would occur for the statements
are suppressed.

--
Tim Young
Elevate Software
www.elevatesoft.com

>> It should be similar - it's the same issue.

Ok - so does that mean it will be fixed in 3.03? ... and while we're on the
subject - any news at all on how it's coming along?

Thanks!

>> It should be similar - it's the same issue.

Ok - so does that mean it will be fixed in 2.03? ... and while we're on the
subject - any news at all on how it's coming along?

Thanks!

Hedley,

<< Ok - so does that mean it will be fixed in 3.03? ... and while we're on
the subject - any news at all on how it's coming along? >>

No, it means that it will be fixed in 2.02 B9, which should be available by
Monday.

--
Tim Young
Elevate Software
www.elevatesoft.com