May 22, 2010 at 4:28 pm
I have few questions on Access to SS2008 upgrade. I wonder what happens exactly behind the scenes i.e architecture wise. Like Once we upgrade a access DB to SS what happens ? Why do we have to keep in mind the data types. Do we create the entire database manually or SS does this automatically. If it were a automatic process .. why do we have to keep up with the changed data types.
what will happen to Forms in the Access dB. ?
I can guess that tables get migrated but what will happen to
Queries?
Forms?
Report?
MAcros?
OR is it that we only upgrade the tables and schema ?
OR Since we have no concept of Forms n Macros .. Do we forget them ?
Please help
Thank You
[font="Verdana"]
Today is the tomorrow you worried about yesterday:-)[/font]
May 23, 2010 at 1:33 am
check out the free SQL Server Migration Assistant for Access (SSMA for Access)
http://www.microsoft.com/sqlserver/2005/en/us/migration-access.aspx
It will point you to some issues and the way to fix them.
Off course, it will only migrate the data objects and the related info.
It will not migrate reports, ...
I haven't tested the SQL2008 version, but the sql2005 version has an option to replace your current tables with linked tables, so your msaccess project will be able to use the sql2005 data.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
May 24, 2010 at 10:51 am
If you use the MS Access Upsizing Wizard in Access or the Migration wizard mentioned above they both work the same way. They "convert" your tables to SQL Server tables. You have options to also move the data, but my experience has been that if you are moving large amounts of data you are better off doing that through SSIS or queries (SQL Server or Access) of your own. You also have the option of linking the SQL Server tables to your Access database and then your Access application queries, forms and reports will basically work the same as they did before. You occasionally run in to a problem here and there, but usually don't end up having to do anything. The upsizing needs to be done from the Access database that contains the actual data. If you have a separate data (back-end) and application (front-end) database as is frequently done then you need to link the tables into the application front-end database. I do this via an ODBC DSN.
To improve performance on certain reports you can consider creating SQL Server views that take the place of Access queries. This is most helpful if you are doing a number of joins and/or selecting only a portion of a lot of data via WHERE clauses with set values. When using views the joining and selection (via WHERE clause) then happens on the SQL Server and will usually be faster than in Access. You can't use parameters in a view so that some times limits what you can do via view.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply