Re: Need tips on moving from MSAccess to MSSQL

Thanks for sharing the path you're taking to upgrade. Gives me some ideas.

Lars.

"Betsy" <betsy.a.tainer@xxxxxxxxxxxxx> skrev i meddelandet
news:4263e97f$1@xxxxxxxxxxxxxxxxxxxxxxxxx
> Not sure this will apply. I'm upgrading a swarm of D5 applications built
> on
> Paradox tables... also some connectivity to as/400 via odbc to retrieve
> data
> from there.
>
> This is the path I've been taking to update:
> -copy data up to sql and modify data types to suit me
> -I take a hard look at the overall data 'configuration' at this time and
> do
> any restructuring here...
> -add ado connection to source (mssql2k)
> -add adotable components to point to tables on sql server
> -point the datasets to the new adocomponents
> -testing compilation along the way for anomolies
>
> -then I start going after the small stuff...
> -I change queries to views on the server
> -change any query requiring a parameter to a stored proc on the server
> -utilize the sql server response as much as it or I am capable... I've
> been
> way impressed with the responsiveness and I've been able to strip out
> reems
> of code out of my application... very clean... it also helps just for
> consistency in the structure which I'm assuming will make troubleshooting
> in
> the future an easier task.
>
> somewhere in there, I check for any functions that are performed in
> response
> to 'scrolling', actions on the old components and port them over to the
> new
> one... once I'm satisfied that I've gotten everything I strip out the old
> component and check for errors.
>
> I've made up this path all by myself. Seems to work good for me... now
> we'll both find out if I'm all screwed up.
>
> b
> "Brian Bushay TeamB" <BBushay@xxxxxxxxx> wrote in message
> news:pfc361to8fbqfr6e6tt96qfqc6c7vnih5c@xxxxxxxxxx
>> >Having applications that today work with MSAccess using dbGO. Now I need
> to
>> >switch to MSSQL.
>> >What have to be changed in the applications?
>>
>> You need to change the OleDbDriver and connectionstring of the
> TadoConnection.
>> Beyond that you may not have to change anything.
>> There are a few differences in SQL so you should check to see that all of
> your
>> queries work.
>> If you are using TableDirect you will have to change that.
>>
>> There may be other things you want to do depending on your reason for
> switching
>> to SQL server and how much you want to optimize your application.
>>
>> --
>> Brian Bushay (TeamB)
>> Bbushay@xxxxxxxxx
>
>


.

Relevant Pages

  • Re: Need tips on moving from MSAccess to MSSQL
    ... also some connectivity to as/400 via odbc to retrieve data ... -utilize the sql server response as much as it or I am capable... ... >>Having applications that today work with MSAccess using dbGO. ...
    (borland.public.delphi.database.ado)
  • RE: after in-place upgrade sql need to re-join domain
    ... Thanks for your response. ... when prior to the upgrade all they entered ... this issue is caused by the wrong Netbios name. ... >> user in SQL server, or on the machine which running SQL Server? ...
    (microsoft.public.windows.server.migration)
  • Performance Hits - Second Post
    ... becoming very frustrated with this performance issue with SQL server - any ... response would be GREATLY appreciated. ... We have recently upgraded 4 SQL servers to Windows 2003, ... experienced this slow performance after the upgrade? ...
    (microsoft.public.sqlserver.server)
  • Re: Upgrading from win2k to win2003
    ... Make sure you have applied SQL Service Pack 3a before running the OS ... The OS upgrade includes a compatibility check for existing ... applications. ... I support the Professional Association for SQL Server ...
    (microsoft.public.sqlserver.server)
  • Re: Application Security
    ... these Windows Forms applications, ASP.NET applications, Windows services, or ... I assume that your C# clients are not distributed to end users. ... > There is a global SQL Server userid and password. ...
    (microsoft.public.dotnet.security)