Re: VB6 SQL Server
From: david epsom dot com dot au (david_at_epsomdotcomdotau)
Date: 04/22/04
- Next message: Warren: "Re: Varialbles with SQL Query's"
- Previous message: maoka: "RDO keep alive, advise needed, pls"
- In reply to: riley: "VB6 SQL Server"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 22 Apr 2004 18:30:42 +1000
>Our main problem, besides database size, is the SLOW process of inserting
massive amounts of
I don't see that converting to SQL Server would fix that.
But, assuming it will somehow:
Check to see if your DAO is use fast, efficient direct access DAO (which
cannot be efficiently converted) or just dao dynasets (which can be
effectively converted to SQL Server attachments). Check to see if you are
using complex Transactions (which can not be effectively converted to use
SQL Server attachment).
(david)
"riley" <mary@mealtimeclm.com> wrote in message
news:C035D35C-7716-45EB-A092-2613B32A59F0@microsoft.com...
> I'm maintaining a legacy VB6/Access 2000 business application. While our
.NET/SQL Server migration is in development, I am considering converting the
existing application to use SQL Server to buy some more time. The
application is a data consolidation and reporting tool using DAO 3.6, with
massive amounts of inline SQL statements and use of DAO recordsets.
>
> My question: Should I consider converting to SQL Server while still using
DAO? Or is a switch to ADO necessary? Our main problem, besides database
size, is the SLOW process of inserting massive amounts of data from multiple
sources (Access databases) into one central database for consolidated
reporting purposes.
>
>
- Next message: Warren: "Re: Varialbles with SQL Query's"
- Previous message: maoka: "RDO keep alive, advise needed, pls"
- In reply to: riley: "VB6 SQL Server"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
