From Access To SQL Server

From Access To SQL Server

Post by Olaf Herde » Thu, 10 Oct 1996 04:00:00



Hello,

we have to migrate an MS Access-application to MS SQL Server 6.5 using
the upsizing wizard.
Does anyone have experience in doing this ?
We are especially interested in tuning the database after migration to
get good performance.

Please answer to this group or email me.

Thank you in advance and greetings from Oldenburg
Olaf

--
******************************************************************

OFFIS                                Telefon     :  0441/9722-188
Escherweg 2                          Sekretariat :           -101
D-26121 Oldenburg                    Fax         :           -102
                                     Privat      :  0441/55436
                               http://www.offis.uni-oldenburg.de/
******************************************************************

 
 
 

From Access To SQL Server

Post by Andrew Fer » Wed, 16 Oct 1996 04:00:00


Hi,
You might be interested in our upsizing wizard that is in final beta.
Our upsizing tool does everything that the MS upsizing tool should but
doesn't do. A large app can be converted in about 8 hours - 35 forms,
300 reports, 400 queries + modules etc. No SQL server admin training
required.
If you are interested please drop me a line.

Regards Andrew Ferry


 
 
 

From Access To SQL Server

Post by Kyle Cord » Wed, 16 Oct 1996 04:00:00



>You might be interested in our upsizing wizard that is in final beta.
>Our upsizing tool does everything that the MS upsizing tool should but
>doesn't do. A large app can be converted in about 8 hours - 35 forms,
>300 reports, 400 queries + modules etc. No SQL server admin training
>required.

What sorts of things does it do?  What are the major problems with the MS
upsizing tool that yours fixes?


 
 
 

From Access To SQL Server

Post by Joe Bolto » Thu, 31 Oct 1996 04:00:00


Sorry, I missed the original messages.  Would developer of the "upsizing
wizard" please let us know the name of the company, contacts, etc.?
Thanks.


___________________________________________________________________




>You might be interested in our upsizing wizard that is in final beta.
>Our upsizing tool does everything that the MS upsizing tool should but
>doesn't do. A large app can be converted in about 8 hours - 35 forms,
>300 reports, 400 queries + modules etc. No SQL server admin training
>required.

What sorts of things does it do?  What are the major problems with the MS
upsizing tool that yours fixes?


 
 
 

From Access To SQL Server

Post by Mike Co » Fri, 01 Nov 1996 04:00:00




> Sorry, I missed the original messages.  Would developer of the
"upsizing
> wizard" please let us know the name of the company, contacts, etc.?
> Thanks.


> ___________________________________________________________________






> >You might be interested in our upsizing wizard that is in final beta.
> >Our upsizing tool does everything that the MS upsizing tool should but
> >doesn't do. A large app can be converted in about 8 hours - 35 forms,
> >300 reports, 400 queries + modules etc. No SQL server admin training
> >required.

> What sorts of things does it do?  What are the major problems with the
MS
> upsizing tool that yours fixes?

The upsizing tool is *very* limited and inflexible. I find it's handy for
creating a table structure in sqlServer, but even then it frequently
requires modification before you populate the tables. It's also god-awful
slow in moving data. BCP is still the only way to go for large tables.

Mike

 
 
 

1. MS ACCESS 97/SQL server 6.5: deadlock problems when accessing server tables

Hi,

we are using ACCESS 97 as front end and SQL Server 6.5 as back end.
When more than one workstation is running our programm these
workstations are more and more often in a "deadlock" state, it seems
they are locking each other out. When this occurs, we are not able to
access the locked server table directly by ISQL/W, too.

Mostly, we access the tables by opening Dynasets by OpenRecordset,
some recordsets are kept globaly open. Actually, the "deadlcok" occurs
when one stattion tries to update a modified recodset to the data
source. My ACCESS doc tells me that ACCESS is not locking linked
tables at all, so _who_ does all this locking ???

Is there any good documentation which tells me exactly what happens
inside ACCESS and SQL Server when ACCESS accesses linked tables ?

Many thanks in advance for your help,

Cheers, Bernd

2. BDE/VCL bug? TUTIL32 (3.12) + BDE 3.12 + explicit load

3. sql server connect. Migration Access->sql server

4. Closing an Open Low-level file

5. LINKING ACCESS TO SQL SERVER DATABASE WITHOUT SQL SERVER INSTALLED (2)

6. Online checkpointing

7. LINKING ACCESS TO SQL SERVER DATABASE WITHOUT SQL SERVER INSTALLED

8. CMAN.ORA and Connection Manager in NET8

9. sql server connect. Migration Access->sql server

10. ACCESS, NT SQL server and Sybase SQL Server

11. Access, ODBC, SQL Server, and Access Write Conflicts

12. Trying to access MS Access from SQL Server