I am experimenting with some different ways of building an .sdf file.

(1) Using RDA, I import the data in my tables from a SQL Server database on
my desktop. This takes about 15 minutes or less.

(2) I export all the data in tab-delimited text files, copy them to the
device, and import them row by row, using SqlCeCommand objects. I realize
that option (1) will be faster, but I am astounded by the difference -- it
takes about 13 hours.

Any explanation as to why the second method is so much less performant? Is
there any way to speed it up? (I have already experimented with removing the
constraints, then adding them after the data has been imported.)

Thx

Helen
--
Helen Warn, PhD
Agile Software Inc.
www.agile-soft.com

I'm not specifically familiar with the SQL Server offering for Win CE, but
can you examine the actual SQL statement being executed for each scenario?
My guess is that the second scenario results in individual logged inserts
which are going to place a greater strain on the database engine.

Colin

"Helen Warn" <(E-Mail Removed)> wrote in message
news:2BE4C549-C532-4018-950D-(E-Mail Removed)...
> I am experimenting with some different ways of building an .sdf file.
>
> (1) Using RDA, I import the data in my tables from a SQL Server database
on
> my desktop. This takes about 15 minutes or less.
>
> (2) I export all the data in tab-delimited text files, copy them to the
> device, and import them row by row, using SqlCeCommand objects. I realize
> that option (1) will be faster, but I am astounded by the difference -- it
> takes about 13 hours.
>
> Any explanation as to why the second method is so much less performant? Is
> there any way to speed it up? (I have already experimented with removing
the
> constraints, then adding them after the data has been imported.)
>
> Thx
>
> Helen
> --
> Helen Warn, PhD
> Agile Software Inc.
> www.agile-soft.com

I'm not sure. Since SQL CE only allows one database connection, it doesn't
seem to make much sense that each row added would result in an individual
logged insert. But clearly there is something causing the non-performance.
Maybe a SQL CE guru will come to my rescue here.

"Colin Young" wrote:

> I'm not specifically familiar with the SQL Server offering for Win CE, but
> can you examine the actual SQL statement being executed for each scenario?
> My guess is that the second scenario results in individual logged inserts
> which are going to place a greater strain on the database engine.
>
> Colin
>