Upsizing Strategies
There are two strategies how database can be migrated from Access to a SQL Server.
- Using ODBC from Microsoft to get access to a remote database via ADO.
- Using Access Projects (available in Microsoft Access 2000 and higher) which allow more "native" integration with Microsoft SQL Server.
The first strategy is often seen as the first step towards complete migration on a SQL server on the stage 2, and can be seen as a part of the strategy 2. For peculiarities of every strategy see the table.
| Parameter | Strategy 1 | Strategy 2 |
|---|---|---|
| Database access | Via ODBC using ADO, somewhat slower than strategy 2. | Native integration with Microsoft SQL Server using Access Project (.adp), data access using ADO |
| Integration | Can be integrated with (almost) any RDBMS | Native support only for Microsoft SQL Server |
| The role of Access | Serves as database front-end with full features of Microsoft Access JET Engine and VBA. (compare to thick client) | Serves as database front-end with limited functionality. Local tables are not allowed. Queries are generally transformed into database views, VBA code manipulating the data is transformed into procedures stored on server. (compare to thin client). |
Read more about this topic: Upsizing (database)
Famous quotes containing the word strategies:
“By intervening in the Vietnamese struggle the United States was attempting to fit its global strategies into a world of hillocks and hamlets, to reduce its majestic concerns for the containment of communism and the security of the Free World to a dimension where governments rose and fell as a result of arguments between two colonels’ wives.”
—Frances Fitzgerald (b. 1940)