Compare
MUST Standard verses MUST+SQL
and find out more about what MUST really Does
Summary:
MUST aims to not only identify, but also automatically FIX common problems,
such as adding primary keys to Access tables, excluding duplicate and
non-selective indexing, identifying and in some cases purifying data for
inconsistencies such as required field issues and illegal date issues. Both
unsecured and secured databases can be processed, and the tool will create a
security mapping to create database roles and schema security on SQL Server.
MUST+SQL gives you an extremely powerful SQL Translation capability, designed to migrate Access specific features such as references to screen controls like Forms!CountryForm!Country into parameter driven Views and Stored Procedures, and can also reconstruct queries into nested queries to support existing complex calculations as described in several articles on this site. Hint: Expand the topics that interest you and print the page.
- Click on the Hyperlinks below to Read More
| MUST Features Comparison | Standard | MUST +SQL |
|---|---|---|
|
Identifies and corrects problems with the upsizing process
The system will identify any problems which could prevent your data being upsized, or lead to future design problems due to missing defaults. In addition to identifying problems the system has tools which will automatically fix the problems.
|
 |
|
| Generates scripts to create tables, upload data and create indexes |
|
|
|
Removes indexes that aren't needed
This is useful way of reducing index clutter in the upsizing process and SQL Server will ignores these unecessary indexes anyway anyway)
|
|
|
|
Supports repeated migrations for commissioning
Supports multiple loads to make for simple commisioning. Commissioning is a process where the existing SQL Server database gets emptied of all test data, and prepared for accepting data from live systems as you switch over to the new systems.
|
|
|
|
Replaces the Access upsizer without the hassle
Easier than Access upsizer if you have a faulty database. The system will identify any problems which could prevent your data being upsized.
|
|
|
|
Action queries are converted to stored procedures
INSERT, UPDATE and DELETE queries are converted to Stored Procedures, which can either be driven using variables (which are inserted in the procedure calls), or by extracting parameters from a parameters table. Other SELECT and CROSSTAB queries are converted to Views.
|
|
|
|
SELECT and CROSSTAB queries are converted to Views
Whilst creating Views is an achievement in itself, what about these features.
1) To resolve problems where calculated columns refer to other calculated columns, MUST automatically creates nested queries. 2) the automatic conversion of query parameters and references to form controls to parameters. 3) Joins on calculated queries and handled by creating Nested queries in SQL Server. |
|
|
|
Identification of Query layering and dependencies
See the dependant queries in a tree view.
All query dependencies are identified (displayed to a maximum of 12 layers). This then enables the tool to allow you to selectively migrate any individual query and automatically identify and include the migration of all dependent query components.
|
|
|
|
Identification of VBA Function calls
Where Access functions have direct equivalents in SQL Server, the tool substitutes existing Access functions with new SQL Server function.
|
|
|
|
Schema support
SQL 2005 and 2008 supports the powerful database schemas and so does MUST+SQL. Read PDF
|
|
|
|
Works with Access databases that are already linked to SQL Server
Works with databases that have been migrated with another upsizer.
If you have an Access application linked to an existing SQL Server 2005 database, then MUST can automatically load the SQL Server data dictionary (list of all tables and fields in the SQL Server) to enable either all or a selected number of Access queries to be migrated.
|
|
|
|
Supports SQL Server 2000/2005/Express/2008
MUST comes with Access 2000, 2002, 2003 and 2007 ready databases so that you can use the version of Access that you have on the version of SQL Server that you want to upsize to.
|
|
|