On 2014-05-27 16:09, Stephen Russell wrote:
On Tue, May 27, 2014 at 1:58 PM, Paul Hill <[email protected]>
wrote:
It depends what the data is. A media file is fine on the HDD.
I have an import process that reads DBFs and converts them into a SQL
database.
Our main app changed from DBF (xBase++) to C# & SQL.
It's not a 1 to 1 process and the import can take many hours. Lots of
seeking.
The SSD excels at this kind of thing.
----------------------
You may find that it is easier to use EF within a C# loader when
posting
the data to the SQL server than the VFP method you currently have. It
is
all a matter of IDs that the server will generate for you needed for
child
table inserts I guess.
Just saying that the transaction time may be less when using EF and
posting
3,5,10+ transactions to the table at once.
I retooled my framework recently, Stephen, using custom character keys.
Although not GUID type explicitly like SQL Server has, they're
definitely GUID-like and 16-bytes long in binary format. I have to say
it's going great so far, and I prefer them now so much more than the
auto-increment integer keys I had used for years. I like controlling
the key generation rather than having the database do it now.
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
