Re: Performance problems moving from ODBC dBase DSN to ODBC SqlServer DSN.
- From: "CharlesC" <Charles@xxxxxxxxxxxxxx>
- Date: Thu, 20 Sep 2007 08:50:54 -0400
Differences between odbc dbase and sql required adjustments to table design
and filters.
Thanks anyway.
"CharlesC" <Charles@xxxxxxxxxxxxxx> wrote in message
news:uiHvlFjyHHA.1176@xxxxxxxxxxxxxxxxxxxxxxx
Hello,identical.
I imported dbf files (dbase) into an msde database.
I see the tables with the data in the msde database. The data is
Recordset's
The only change made to the code is in the DSN assignment in the
GetDefaultConnect(),the
return _T("ODBC;DSN=themsde").
Both DSN's are ODBC, the original uses Microsoft dBase driver (dbf),
the msde is of course SQL Server.
Using the SAME data and the SAME code I add a record (AddNew())
the Recordset.Open() takes about 4 or 5 times longer with the msde dsn
the Recordset.Update() takes about 10 times longer (eg. 10 seconds with
msde dsn, less than 1 with dbase odbc dsn)
Are there changes that have to be made in the code or in the data?
Thanks.
.
- Prev by Date: Re: ODBC & Remote SQL Server
- Next by Date: Re: Linking Access 2003 to SQL 2005
- Previous by thread: ODBC & Remote SQL Server
- Next by thread: Re: Linking Access 2003 to SQL 2005
- Index(es):
Relevant Pages
|
Loading