[AccessD] Moving to SQL Server

For me, the best choice would be to allow the developer to choose.
However, in a very large application, that could become quite a burden,
so it would be nice if there were some intelligent groupings you could
use, like queries in objects or nested queries, for example.  Simple
queries can become views.  Parameter queries have to be stored
procedures or UDFs.  The developer should have to specify queries to
convert to UDFs but nested queries should be handled as a group and
converted to a single SP or UDF without the developer having to do all
the donkey work.

I'd prefer an optional wizard with developer override.


Charlotte Foust

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Martin Reid
Sent: Tuesday, June 13, 2006 2:04 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] Moving to SQL Server

Hi
 
I am working (sort of with) the development people for the new SQL
Server 2005 Migration Assistant. Anyway. When moving queries etc to SQL
Server what server side objects should they be converted to
 
Stored Procedures
Views
Passs Throughs
UDFs
 
Or should the developer have the choice. Say a dialog which listed the
objects and allowed oyu to pick the most appropriate.
I am interesteed in teh real work developers do as the primary focus of
the assistant is developers. 
 
Would a wizartd driven interface help or would you prefer no wizard. If
there was a wizard would you want it to do the whole thing or just
prepare the databsae and then let you manually adjust things like
queries and data types?
 
How would you like queries in form objects handled?
 
So what do you think?
 
All comments etc will be passed on to the development group.
 
Martin
 
 
 
Martin WP Reid
Training and Assessment Unit
Riddle Hall
Belfast
 
tel: 02890 974477