|
|
Posted by Ben on 02/05/07 06:09
Wes,
Just a thought. What are you trying to accomplish with the migration or
upsizing of your Access application? What is the Access version?
I used the Upsize Wizard to upsize our Access application. It went well
after I cleared all issues with my Access database. The Access
database structure is less strict and was meant to work on itself. Due to
the imperfections of the Access database the upsize wizard oftentimes
end up giving you a lot of errors the first or even 5th time. This is true
if I use even SQL Server 2005 Express. The data in the Access database
will also cause the upsize wizard to crash because SQL Server will not allow
erroneous data to creep into its tables.
FYI, using DTS will not expose all Access database problems also. You have
to understand and know which errors are caused by what.
Once you successfully upsized your access table, then you can concentrate on
deciding either to keep the queries or create views and stored
procedures in the SQL Server. This approach will be of help to you when you
link the tables from SQL Server in your Access application.
If you also try to google "Upsizing Access to SQL Server", you should find
more information regarding your task.
I also encourage you to use the Upsize Wizard of Access because that is why
it is there. It will definitely be quicker for you in the long run.
The upsize wizard if the access database or data have problems.
Based on my experience, the simplest approach (less work/change approach) is
usually the correct one.
"Wes Groleau" <groleau+news@freeshell.org> wrote in message
news:1Yyxh.1926$5U4.1714@trnddc07...
> Steve wrote:
>> On Feb 3, 12:24 pm, Wes Groleau <groleau+n...@freeshell.org> wrote:
>>> When I try to import from Access, the DTS wizard only allows me to
>>> import tables and queries. OK, I'm not surprised the "macros" and
>>> reports don't come over.
>>>
>>> But it executes each query, and created a _table_ to hold the results.
>>>
>>> The sensible thing would be that SELECT queries become views
>>> and the others become stored procedures. But I find no way
>>> controls I can select to do that.
>>>
>>> I have to manually create the views/procedures and paste in the SQL.
>>> And then I still have to translate it into standard SQL.
>>>
>>> --
>>> Wes Groleau
>>>
>>> Beware of the man who works hard to learn something, learns
>>> it, and finds himself no wiser than before ... He is full of
>>> murderous resentment of people who are ignorant without having
>>> come by their ignorance the hard way.
>>> -- Kurt Vonnegut
>>
>> Did you try the SQL Server Migration Assistant for Access?
>> http://www.microsoft.com/sql/solutions/migration/access/default.mspx
>
> No. That's SQL Server 2005. Thanks anyway.
>
> --
> Wes Groleau
>
> In any formula, constants (especially those obtained
> from handbooks) are to be treated as variables.
[Back to original message]
|