Wednesday, April 20, 2011

Output Logs for Canceled Migration of Northwind.accdb to a SQL Server Northwind Database with SSMA for Access

Attempting to migrate the tables of an Access 2010 Northwind.accdb database created from the built-in Northwind template with the SQL Server Migration Assistant for Access v4.2 generates 670 log entries for 20 tables. The entries consist of 6 error, 245 warning, 233 information and 116 other messages.

Migration failed because of five instances of Access tables with unsupported Attachment field data types and one instance of an unsupported Lookup field data type. Many warnings are the result of the Access team’s inexplicable inclusion of spaces in field names.

Following is a complete copy of these log entries:

Starting conversion...
Analyzing metadata...
Converting table Northwind.[Customers] ...
Warnings: A2SS0030: Column 'Last Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'First Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'E-mail Address' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Job Title' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Business Phone' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Home Phone' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Mobile Phone' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Fax Number' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'State/Province' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'ZIP/Postal Code' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Country/Region' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Web Page' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0021: The hyperlink column 'Web Page' was converted to a text column and, as a result, is no longer a link.
Errors: A2SS0070: Attachment datatype is not supported.
Information: A2SS0029: Primary key name 'PrimaryKey' was changed during conversion.
Information: A2SS0029: Index name 'City' was changed during conversion.
Information: A2SS0029: Index name 'Company' was changed during conversion.
Information: A2SS0029: Index name 'First Name' was changed during conversion.
Warnings: A2SS0030: Index 'First Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'Last Name' was changed during conversion.
Warnings: A2SS0030: Index 'Last Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'Postal Code' was changed during conversion.
Warnings: A2SS0030: Index 'Postal Code' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'State/Province' was changed during conversion.
Warnings: A2SS0030: Index 'State/Province' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Company' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Last Name' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'First Name' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'E-mail Address' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Job Title' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Business Phone' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Home Phone' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Mobile Phone' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Fax Number' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Address' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'City' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'State/Province' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'ZIP/Postal Code' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Country/Region' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Web Page' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Notes' was converted to a check constraint.
Information: A2SS0020: New timestamp column 'SSMA_TimeStamp' created.
Converting table Northwind.[Employee Privileges] ...
Warnings: A2SS0030: Column 'Employee ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Privilege ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Primary key name 'PrimaryKey' was changed during conversion.
Warnings: A2SS0030: Primary key 'PrimaryKey' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Foreign key name 'New_EmployeePriviligesforEmployees' was changed during conversion.
Warnings: A2SS0030: Foreign key 'New_EmployeePriviligesforEmployees' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Foreign key name 'New_EmployeePriviligesLookup' was changed during conversion.
Warnings: A2SS0030: Foreign key 'New_EmployeePriviligesLookup' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'EmployeePriviligesforEmployees' was changed during conversion.
Warnings: A2SS0030: Index 'EmployeePriviligesforEmployees' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'EmployeePriviligesLookup' was changed during conversion.
Warnings: A2SS0030: Index 'EmployeePriviligesLookup' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'New_EmployeePriviligesforEmployees' was changed during conversion.
Warnings: A2SS0030: Index 'New_EmployeePriviligesforEmployees' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'New_EmployeePriviligesLookup' was changed during conversion.
Warnings: A2SS0030: Index 'New_EmployeePriviligesLookup' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'Privilege ID' was changed during conversion.
Warnings: A2SS0030: Index 'Privilege ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Table 'Employee Privileges' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0016: Column 'C:\USERS\ADMINISTRATOR\DOCUMENTS\NORTHWIND.ACCDB.EMPLOYEE PRIVILEGES.EMPLOYEE ID' of the primary key is nullable, which SQL Server does not allow. The nullable flag was removed from the target column to avoid problems during loading database objects into SQL Server. If there are rows that contain NULL values, you might encounter problems during data migration.
Warnings: A2SS0016: Column 'C:\USERS\ADMINISTRATOR\DOCUMENTS\NORTHWIND.ACCDB.EMPLOYEE PRIVILEGES.PRIVILEGE ID' of the primary key is nullable, which SQL Server does not allow. The nullable flag was removed from the target column to avoid problems during loading database objects into SQL Server. If there are rows that contain NULL values, you might encounter problems during data migration.
Converting table Northwind.[Employees] ...
Warnings: A2SS0030: Column 'Last Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'First Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'E-mail Address' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Job Title' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Business Phone' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Home Phone' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Mobile Phone' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Fax Number' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'State/Province' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'ZIP/Postal Code' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Country/Region' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Web Page' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0021: The hyperlink column 'Web Page' was converted to a text column and, as a result, is no longer a link.
Errors: A2SS0070: Attachment datatype is not supported.
Information: A2SS0029: Primary key name 'PrimaryKey' was changed during conversion.
Information: A2SS0029: Index name 'City' was changed during conversion.
Information: A2SS0029: Index name 'Company' was changed during conversion.
Information: A2SS0029: Index name 'First Name' was changed during conversion.
Warnings: A2SS0030: Index 'First Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'Last Name' was changed during conversion.
Warnings: A2SS0030: Index 'Last Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'Postal Code' was changed during conversion.
Warnings: A2SS0030: Index 'Postal Code' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'State/Province' was changed during conversion.
Warnings: A2SS0030: Index 'State/Province' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Company' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Last Name' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'First Name' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'E-mail Address' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Job Title' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Business Phone' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Home Phone' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Mobile Phone' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Fax Number' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Address' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'City' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'State/Province' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'ZIP/Postal Code' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Country/Region' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Web Page' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Notes' was converted to a check constraint.
Information: A2SS0020: New timestamp column 'SSMA_TimeStamp' created.
Converting table Northwind.[Inventory Transaction Types] ...
Warnings: A2SS0030: Column 'Type Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Primary key name 'PrimaryKey' was changed during conversion.
Warnings: A2SS0030: Primary key 'PrimaryKey' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Table 'Inventory Transaction Types' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Type Name' was converted to a check constraint.
Warnings: A2SS0016: Column 'C:\USERS\ADMINISTRATOR\DOCUMENTS\NORTHWIND.ACCDB.INVENTORY TRANSACTION TYPES.ID' of the primary key is nullable, which SQL Server does not allow. The nullable flag was removed from the target column to avoid problems during loading database objects into SQL Server. If there are rows that contain NULL values, you might encounter problems during data migration.
Converting table Northwind.[Inventory Transactions] ...
Warnings: A2SS0030: Column 'Transaction ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Transaction Type' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Transaction Created Date' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Transaction Modified Date' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Product ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Purchase Order ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Customer Order ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Primary key name 'PrimaryKey' was changed during conversion.
Warnings: A2SS0030: Primary key 'PrimaryKey' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Foreign key name 'New_OrdersOnInventoryTransactions' was changed during conversion.
Warnings: A2SS0030: Foreign key 'New_OrdersOnInventoryTransactions' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Foreign key name 'New_ProductOnInventoryTransaction' was changed during conversion.
Warnings: A2SS0030: Foreign key 'New_ProductOnInventoryTransaction' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Foreign key name 'New_PuchaseOrdersonInventoryTransactions' was changed during conversion.
Warnings: A2SS0030: Foreign key 'New_PuchaseOrdersonInventoryTransactions' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Foreign key name 'New_TransactionTypesOnInventoryTransactiosn' was changed during conversion.
Warnings: A2SS0030: Foreign key 'New_TransactionTypesOnInventoryTransactiosn' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'Customer Order ID' was changed during conversion.
Warnings: A2SS0030: Index 'Customer Order ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'New_OrdersOnInventoryTransactions' was changed during conversion.
Warnings: A2SS0030: Index 'New_OrdersOnInventoryTransactions' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'New_ProductOnInventoryTransaction' was changed during conversion.
Warnings: A2SS0030: Index 'New_ProductOnInventoryTransaction' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'New_PuchaseOrdersonInventoryTransactions' was changed during conversion.
Warnings: A2SS0030: Index 'New_PuchaseOrdersonInventoryTransactions' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'New_TransactionTypesOnInventoryTransactiosn' was changed during conversion.
Warnings: A2SS0030: Index 'New_TransactionTypesOnInventoryTransactiosn' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'OrdersOnInventoryTransactions' was changed during conversion.
Warnings: A2SS0030: Index 'OrdersOnInventoryTransactions' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'Product ID' was changed during conversion.
Warnings: A2SS0030: Index 'Product ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'ProductOnInventoryTransaction' was changed during conversion.
Warnings: A2SS0030: Index 'ProductOnInventoryTransaction' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'PuchaseOrdersonInventoryTransactions' was changed during conversion.
Warnings: A2SS0030: Index 'PuchaseOrdersonInventoryTransactions' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'Purchase Order ID' was changed during conversion.
Warnings: A2SS0030: Index 'Purchase Order ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'TransactionTypesOnInventoryTransactiosn' was changed during conversion.
Warnings: A2SS0030: Index 'TransactionTypesOnInventoryTransactiosn' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Table 'Inventory Transactions' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Comments' was converted to a check constraint.
Converting table Northwind.[Invoices] ...
Warnings: A2SS0030: Column 'Invoice ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Order ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Invoice Date' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Due Date' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Amount Due' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Primary key name 'PrimaryKey' was changed during conversion.
Information: A2SS0029: Foreign key name 'New_OrderInvoice' was changed during conversion.
Information: A2SS0029: Index name 'New_OrderInvoice' was changed during conversion.
Information: A2SS0029: Index name 'Order ID' was changed during conversion.
Warnings: A2SS0030: Index 'Order ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'OrderInvoice' was changed during conversion.
Converting table Northwind.[Order Details] ...
Warnings: A2SS0030: Column 'Order ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Product ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Unit Price' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Status ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Date Allocated' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Purchase Order ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Inventory ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Primary key name 'PrimaryKey' was changed during conversion.
Warnings: A2SS0030: Primary key 'PrimaryKey' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Foreign key name 'New_OrderDetails' was changed during conversion.
Warnings: A2SS0030: Foreign key 'New_OrderDetails' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Foreign key name 'New_OrderStatusLookup' was changed during conversion.
Warnings: A2SS0030: Foreign key 'New_OrderStatusLookup' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Foreign key name 'New_ProductsOnOrders' was changed during conversion.
Warnings: A2SS0030: Foreign key 'New_ProductsOnOrders' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'ID' was changed during conversion.
Warnings: A2SS0030: Index 'ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'Inventory ID' was changed during conversion.
Warnings: A2SS0030: Index 'Inventory ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'New_OrderDetails' was changed during conversion.
Warnings: A2SS0030: Index 'New_OrderDetails' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'New_OrderStatusLookup' was changed during conversion.
Warnings: A2SS0030: Index 'New_OrderStatusLookup' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'New_ProductsOnOrders' was changed during conversion.
Warnings: A2SS0030: Index 'New_ProductsOnOrders' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'OrderDetails' was changed during conversion.
Warnings: A2SS0030: Index 'OrderDetails' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'OrderID' was changed during conversion.
Warnings: A2SS0030: Index 'OrderID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'OrderStatusLookup' was changed during conversion.
Warnings: A2SS0030: Index 'OrderStatusLookup' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'ProductID' was changed during conversion.
Warnings: A2SS0030: Index 'ProductID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'ProductsOnOrders' was changed during conversion.
Warnings: A2SS0030: Index 'ProductsOnOrders' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'Purchase Order ID' was changed during conversion.
Warnings: A2SS0030: Index 'Purchase Order ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'Status ID' was changed during conversion.
Warnings: A2SS0030: Index 'Status ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Table 'Order Details' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0020: New timestamp column 'SSMA_TimeStamp' created.
Converting table Northwind.[Order Details Status] ...
Warnings: A2SS0030: Column 'Status ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Status Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Primary key name 'PrimaryKey' was changed during conversion.
Warnings: A2SS0030: Primary key 'PrimaryKey' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Table 'Order Details Status' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Status Name' was converted to a check constraint.
Warnings: A2SS0016: Column 'C:\USERS\ADMINISTRATOR\DOCUMENTS\NORTHWIND.ACCDB.ORDER DETAILS STATUS.STATUS ID' of the primary key is nullable, which SQL Server does not allow. The nullable flag was removed from the target column to avoid problems during loading database objects into SQL Server. If there are rows that contain NULL values, you might encounter problems during data migration.
Converting table Northwind.[Orders] ...
Warnings: A2SS0030: Column 'Order ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Employee ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Customer ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Order Date' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Shipped Date' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Shipper ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Ship Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Ship Address' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Ship City' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Ship State/Province' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Ship ZIP/Postal Code' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Ship Country/Region' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Shipping Fee' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Payment Type' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Paid Date' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Tax Rate' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Tax Status' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Status ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Primary key name 'PrimaryKey' was changed during conversion.
Information: A2SS0029: Foreign key name 'New_CustomerOnOrders' was changed during conversion.
Information: A2SS0029: Foreign key name 'New_EmployeesOnOrders' was changed during conversion.
Information: A2SS0029: Foreign key name 'New_OrderStatus' was changed during conversion.
Information: A2SS0029: Foreign key name 'New_ShipperOnOrder' was changed during conversion.
Information: A2SS0029: Foreign key name 'New_TaxStatusOnOrders' was changed during conversion.
Information: A2SS0029: Index name 'CustomerID' was changed during conversion.
Information: A2SS0029: Index name 'CustomerOnOrders' was changed during conversion.
Information: A2SS0029: Index name 'EmployeeID' was changed during conversion.
Information: A2SS0029: Index name 'EmployeesOnOrders' was changed during conversion.
Information: A2SS0029: Index name 'ID' was changed during conversion.
Information: A2SS0029: Index name 'New_CustomerOnOrders' was changed during conversion.
Information: A2SS0029: Index name 'New_EmployeesOnOrders' was changed during conversion.
Information: A2SS0029: Index name 'New_OrderStatus' was changed during conversion.
Information: A2SS0029: Index name 'New_ShipperOnOrder' was changed during conversion.
Information: A2SS0029: Index name 'New_TaxStatusOnOrders' was changed during conversion.
Information: A2SS0029: Index name 'OrderStatus' was changed during conversion.
Information: A2SS0029: Index name 'ShipperID' was changed during conversion.
Information: A2SS0029: Index name 'ShipperOnOrder' was changed during conversion.
Information: A2SS0029: Index name 'Status ID' was changed during conversion.
Warnings: A2SS0030: Index 'Status ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'TaxStatusOnOrders' was changed during conversion.
Information: A2SS0029: Index name 'ZIP/Postal Code' was changed during conversion.
Warnings: A2SS0030: Index 'ZIP/Postal Code' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Ship Name' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Ship Address' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Ship City' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Ship State/Province' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Ship ZIP/Postal Code' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Ship Country/Region' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Payment Type' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Notes' was converted to a check constraint.
Information: A2SS0020: New timestamp column 'SSMA_TimeStamp' created.
Converting table Northwind.[Orders Status] ...
Warnings: A2SS0030: Column 'Status ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Status Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Primary key name 'PrimaryKey' was changed during conversion.
Warnings: A2SS0030: Primary key 'PrimaryKey' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Table 'Orders Status' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Status Name' was converted to a check constraint.
Warnings: A2SS0016: Column 'C:\USERS\ADMINISTRATOR\DOCUMENTS\NORTHWIND.ACCDB.ORDERS STATUS.STATUS ID' of the primary key is nullable, which SQL Server does not allow. The nullable flag was removed from the target column to avoid problems during loading database objects into SQL Server. If there are rows that contain NULL values, you might encounter problems during data migration.
Converting table Northwind.[Orders Tax Status] ...
Warnings: A2SS0030: Column 'Tax Status Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Primary key name 'PrimaryKey' was changed during conversion.
Warnings: A2SS0030: Primary key 'PrimaryKey' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Table 'Orders Tax Status' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Tax Status Name' was converted to a check constraint.
Warnings: A2SS0016: Column 'C:\USERS\ADMINISTRATOR\DOCUMENTS\NORTHWIND.ACCDB.ORDERS TAX STATUS.ID' of the primary key is nullable, which SQL Server does not allow. The nullable flag was removed from the target column to avoid problems during loading database objects into SQL Server. If there are rows that contain NULL values, you might encounter problems during data migration.
Converting table Northwind.[Privileges] ...
Warnings: A2SS0030: Column 'Privilege ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Privilege Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Primary key name 'PrimaryKey' was changed during conversion.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Privilege Name' was converted to a check constraint.
Converting table Northwind.[Products] ...
Warnings: A2SS0030: Column 'Supplier IDs' has a name that might cause problems for the Access application to function correctly against SQL Server.
Errors: A2SS0070: ComplexLong datatype is not supported.
Warnings: A2SS0030: Column 'Product Code' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Product Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Standard Cost' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'List Price' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Reorder Level' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Target Level' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Quantity Per Unit' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Minimum Reorder Quantity' has a name that might cause problems for the Access application to function correctly against SQL Server.
Errors: A2SS0070: Attachment datatype is not supported.
Information: A2SS0029: Primary key name 'PrimaryKey' was changed during conversion.
Information: A2SS0029: Index name 'Product Code' was changed during conversion.
Warnings: A2SS0030: Index 'Product Code' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Product Code' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Product Name' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Description' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Quantity Per Unit' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Category' was converted to a check constraint.
Information: A2SS0020: New timestamp column 'SSMA_TimeStamp' created.
Converting table Northwind.[Purchase Order Details] ...
Warnings: A2SS0030: Column 'Purchase Order ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Product ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Unit Cost' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Date Received' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Posted To Inventory' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Inventory ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Primary key name 'PrimaryKey' was changed during conversion.
Warnings: A2SS0030: Primary key 'PrimaryKey' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Foreign key name 'New_InventoryTransactionsOnPurchaseOrders' was changed during conversion.
Warnings: A2SS0030: Foreign key 'New_InventoryTransactionsOnPurchaseOrders' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Foreign key name 'New_ProductOnPurchaseOrderDetails' was changed during conversion.
Warnings: A2SS0030: Foreign key 'New_ProductOnPurchaseOrderDetails' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Foreign key name 'New_PurchaseOrderDeatilsOnPurchaseOrder' was changed during conversion.
Warnings: A2SS0030: Foreign key 'New_PurchaseOrderDeatilsOnPurchaseOrder' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'ID' was changed during conversion.
Warnings: A2SS0030: Index 'ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'Inventory ID' was changed during conversion.
Warnings: A2SS0030: Index 'Inventory ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'InventoryTransactionsOnPurchaseOrders' was changed during conversion.
Warnings: A2SS0030: Index 'InventoryTransactionsOnPurchaseOrders' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'New_InventoryTransactionsOnPurchaseOrders' was changed during conversion.
Warnings: A2SS0030: Index 'New_InventoryTransactionsOnPurchaseOrders' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'New_ProductOnPurchaseOrderDetails' was changed during conversion.
Warnings: A2SS0030: Index 'New_ProductOnPurchaseOrderDetails' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'New_PurchaseOrderDeatilsOnPurchaseOrder' was changed during conversion.
Warnings: A2SS0030: Index 'New_PurchaseOrderDeatilsOnPurchaseOrder' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'OrderID' was changed during conversion.
Warnings: A2SS0030: Index 'OrderID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'ProductID' was changed during conversion.
Warnings: A2SS0030: Index 'ProductID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'ProductOnPurchaseOrderDetails' was changed during conversion.
Warnings: A2SS0030: Index 'ProductOnPurchaseOrderDetails' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'PurchaseOrderDeatilsOnPurchaseOrder' was changed during conversion.
Warnings: A2SS0030: Index 'PurchaseOrderDeatilsOnPurchaseOrder' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Table 'Purchase Order Details' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0020: New timestamp column 'SSMA_TimeStamp' created.
Converting table Northwind.[Purchase Order Status] ...
Warnings: A2SS0030: Column 'Status ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Primary key name 'PrimaryKey' was changed during conversion.
Warnings: A2SS0030: Primary key 'PrimaryKey' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Table 'Purchase Order Status' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Status' was converted to a check constraint.
Warnings: A2SS0016: Column 'C:\USERS\ADMINISTRATOR\DOCUMENTS\NORTHWIND.ACCDB.PURCHASE ORDER STATUS.STATUS ID' of the primary key is nullable, which SQL Server does not allow. The nullable flag was removed from the target column to avoid problems during loading database objects into SQL Server. If there are rows that contain NULL values, you might encounter problems during data migration.
Converting table Northwind.[Purchase Orders] ...
Warnings: A2SS0030: Column 'Purchase Order ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Supplier ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Created By' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Submitted Date' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Creation Date' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Status ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Expected Date' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Shipping Fee' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Payment Date' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Payment Amount' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Payment Method' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Approved By' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Approved Date' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Submitted By' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Primary key name 'PrimaryKey' was changed during conversion.
Warnings: A2SS0030: Primary key 'PrimaryKey' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Foreign key name 'New_EmployeesOnPurchaseOrder' was changed during conversion.
Warnings: A2SS0030: Foreign key 'New_EmployeesOnPurchaseOrder' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Foreign key name 'New_PurchaseOrderStatusLookup' was changed during conversion.
Warnings: A2SS0030: Foreign key 'New_PurchaseOrderStatusLookup' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Foreign key name 'New_SuppliersOnPurchaseOrder' was changed during conversion.
Warnings: A2SS0030: Foreign key 'New_SuppliersOnPurchaseOrder' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'EmployeesOnPurchaseOrder' was changed during conversion.
Warnings: A2SS0030: Index 'EmployeesOnPurchaseOrder' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'ID' was changed during conversion.
Warnings: A2SS0030: Index 'ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'New_EmployeesOnPurchaseOrder' was changed during conversion.
Warnings: A2SS0030: Index 'New_EmployeesOnPurchaseOrder' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'New_PurchaseOrderStatusLookup' was changed during conversion.
Warnings: A2SS0030: Index 'New_PurchaseOrderStatusLookup' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'New_SuppliersOnPurchaseOrder' was changed during conversion.
Warnings: A2SS0030: Index 'New_SuppliersOnPurchaseOrder' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'PurchaseOrderStatusLookup' was changed during conversion.
Warnings: A2SS0030: Index 'PurchaseOrderStatusLookup' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'Status ID' was changed during conversion.
Warnings: A2SS0030: Index 'Status ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'SupplierID' was changed during conversion.
Warnings: A2SS0030: Index 'SupplierID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'SuppliersOnPurchaseOrder' was changed during conversion.
Warnings: A2SS0030: Index 'SuppliersOnPurchaseOrder' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Table 'Purchase Orders' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Payment Method' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Notes' was converted to a check constraint.
Information: A2SS0020: New timestamp column 'SSMA_TimeStamp' created.
Converting table Northwind.[Sales Reports] ...
Warnings: A2SS0030: Column 'Group By' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Filter Row Source' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Default' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Primary key name 'PrimaryKey' was changed during conversion.
Warnings: A2SS0030: Primary key 'PrimaryKey' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Table 'Sales Reports' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Group By' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Display' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Title' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Filter Row Source' was converted to a check constraint.
Information: A2SS0020: New timestamp column 'SSMA_TimeStamp' created.
Converting table Northwind.[Shippers] ...
Warnings: A2SS0030: Column 'Last Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'First Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'E-mail Address' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Job Title' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Business Phone' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Home Phone' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Mobile Phone' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Fax Number' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'State/Province' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'ZIP/Postal Code' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Country/Region' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Web Page' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0021: The hyperlink column 'Web Page' was converted to a text column and, as a result, is no longer a link.
Errors: A2SS0070: Attachment datatype is not supported.
Information: A2SS0029: Primary key name 'PrimaryKey' was changed during conversion.
Information: A2SS0029: Index name 'City' was changed during conversion.
Information: A2SS0029: Index name 'Company' was changed during conversion.
Information: A2SS0029: Index name 'First Name' was changed during conversion.
Warnings: A2SS0030: Index 'First Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'Last Name' was changed during conversion.
Warnings: A2SS0030: Index 'Last Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'Postal Code' was changed during conversion.
Warnings: A2SS0030: Index 'Postal Code' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'State/Province' was changed during conversion.
Warnings: A2SS0030: Index 'State/Province' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Company' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Last Name' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'First Name' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'E-mail Address' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Job Title' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Business Phone' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Home Phone' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Mobile Phone' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Fax Number' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Address' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'City' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'State/Province' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'ZIP/Postal Code' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Country/Region' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Web Page' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Notes' was converted to a check constraint.
Information: A2SS0020: New timestamp column 'SSMA_TimeStamp' created.
Converting table Northwind.[Strings] ...
Warnings: A2SS0030: Column 'String ID' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'String Data' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Primary key name 'PrimaryKey' was changed during conversion.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'String Data' was converted to a check constraint.
Converting table Northwind.[Suppliers] ...
Warnings: A2SS0030: Column 'Last Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'First Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'E-mail Address' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Job Title' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Business Phone' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Home Phone' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Mobile Phone' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Fax Number' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'State/Province' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'ZIP/Postal Code' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Country/Region' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0030: Column 'Web Page' has a name that might cause problems for the Access application to function correctly against SQL Server.
Warnings: A2SS0021: The hyperlink column 'Web Page' was converted to a text column and, as a result, is no longer a link.
Errors: A2SS0070: Attachment datatype is not supported.
Information: A2SS0029: Primary key name 'PrimaryKey' was changed during conversion.
Information: A2SS0029: Index name 'City' was changed during conversion.
Information: A2SS0029: Index name 'Company' was changed during conversion.
Information: A2SS0029: Index name 'First Name' was changed during conversion.
Warnings: A2SS0030: Index 'First Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'Last Name' was changed during conversion.
Warnings: A2SS0030: Index 'Last Name' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'Postal Code' was changed during conversion.
Warnings: A2SS0030: Index 'Postal Code' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0029: Index name 'State/Province' was changed during conversion.
Warnings: A2SS0030: Index 'State/Province' has a name that might cause problems for the Access application to function correctly against SQL Server.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Company' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Last Name' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'First Name' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'E-mail Address' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Job Title' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Business Phone' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Home Phone' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Mobile Phone' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Fax Number' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Address' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'City' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'State/Province' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'ZIP/Postal Code' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Country/Region' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Web Page' was converted to a check constraint.
Information: A2SS0005: The Zero-length-not-allowed flag on the column 'Notes' was converted to a check constraint.
Information: A2SS0020: New timestamp column 'SSMA_TimeStamp' created.
Conversion finished with 6 errors, 245 warnings, and 233 informational messages.
Loading objects into database...
Analyzing metadata...
Preparing category Tables of schema Northwind.dbo...
Preparing table Northwind.dbo.[Customers]...
Preparing category Triggers of table Northwind.dbo.[Customers]...
Preparing category Indexes of table Northwind.dbo.[Customers]...
Preparing index Northwind.dbo.[Customers].[Customers$City]...
Preparing index Northwind.dbo.[Customers].[Customers$Company]...
Preparing index Northwind.dbo.[Customers].[Customers$First Name]...
Preparing index Northwind.dbo.[Customers].[Customers$Last Name]...
Preparing index Northwind.dbo.[Customers].[Customers$Postal Code]...
Preparing index Northwind.dbo.[Customers].[Customers$State/Province]...
Preparing table Northwind.dbo.[Employee Privileges]...
Preparing category Triggers of table Northwind.dbo.[Employee Privileges]...
Preparing category Indexes of table Northwind.dbo.[Employee Privileges]...
Preparing index Northwind.dbo.[Employee Privileges].[Employee Privileges$EmployeePriviligesforEmployees]...
Preparing index Northwind.dbo.[Employee Privileges].[Employee Privileges$EmployeePriviligesLookup]...
Preparing index Northwind.dbo.[Employee Privileges].[Employee Privileges$New_EmployeePriviligesforEmployees]...
Preparing index Northwind.dbo.[Employee Privileges].[Employee Privileges$New_EmployeePriviligesLookup]...
Preparing index Northwind.dbo.[Employee Privileges].[Employee Privileges$Privilege ID]...
Preparing table Northwind.dbo.[Employees]...
Preparing category Triggers of table Northwind.dbo.[Employees]...
Preparing category Indexes of table Northwind.dbo.[Employees]...
Preparing index Northwind.dbo.[Employees].[Employees$City]...
Preparing index Northwind.dbo.[Employees].[Employees$Company]...
Preparing index Northwind.dbo.[Employees].[Employees$First Name]...
Preparing index Northwind.dbo.[Employees].[Employees$Last Name]...
Preparing index Northwind.dbo.[Employees].[Employees$Postal Code]...
Preparing index Northwind.dbo.[Employees].[Employees$State/Province]...
Preparing table Northwind.dbo.[Inventory Transaction Types]...
Preparing category Triggers of table Northwind.dbo.[Inventory Transaction Types]...
Preparing category Indexes of table Northwind.dbo.[Inventory Transaction Types]...
Preparing table Northwind.dbo.[Inventory Transactions]...
Preparing category Triggers of table Northwind.dbo.[Inventory Transactions]...
Preparing category Indexes of table Northwind.dbo.[Inventory Transactions]...
Preparing index Northwind.dbo.[Inventory Transactions].[Inventory Transactions$Customer Order ID]...
Preparing index Northwind.dbo.[Inventory Transactions].[Inventory Transactions$New_OrdersOnInventoryTransactions]...
Preparing index Northwind.dbo.[Inventory Transactions].[Inventory Transactions$New_ProductOnInventoryTransaction]...
Preparing index Northwind.dbo.[Inventory Transactions].[Inventory Transactions$New_PuchaseOrdersonInventoryTransactions]...
Preparing index Northwind.dbo.[Inventory Transactions].[Inventory Transactions$New_TransactionTypesOnInventoryTransactiosn]...
Preparing index Northwind.dbo.[Inventory Transactions].[Inventory Transactions$OrdersOnInventoryTransactions]...
Preparing index Northwind.dbo.[Inventory Transactions].[Inventory Transactions$Product ID]...
Preparing index Northwind.dbo.[Inventory Transactions].[Inventory Transactions$ProductOnInventoryTransaction]...
Preparing index Northwind.dbo.[Inventory Transactions].[Inventory Transactions$PuchaseOrdersonInventoryTransactions]...
Preparing index Northwind.dbo.[Inventory Transactions].[Inventory Transactions$Purchase Order ID]...
Preparing index Northwind.dbo.[Inventory Transactions].[Inventory Transactions$TransactionTypesOnInventoryTransactiosn]...
Preparing table Northwind.dbo.[Invoices]...
Preparing category Triggers of table Northwind.dbo.[Invoices]...
Preparing category Indexes of table Northwind.dbo.[Invoices]...
Preparing index Northwind.dbo.[Invoices].[Invoices$New_OrderInvoice]...
Preparing index Northwind.dbo.[Invoices].[Invoices$Order ID]...
Preparing index Northwind.dbo.[Invoices].[Invoices$OrderInvoice]...
Preparing table Northwind.dbo.[Order Details]...
Preparing category Triggers of table Northwind.dbo.[Order Details]...
Preparing category Indexes of table Northwind.dbo.[Order Details]...
Preparing index Northwind.dbo.[Order Details].[Order Details$ID]...
Preparing index Northwind.dbo.[Order Details].[Order Details$Inventory ID]...
Preparing index Northwind.dbo.[Order Details].[Order Details$New_OrderDetails]...
Preparing index Northwind.dbo.[Order Details].[Order Details$New_OrderStatusLookup]...
Preparing index Northwind.dbo.[Order Details].[Order Details$New_ProductsOnOrders]...
Preparing index Northwind.dbo.[Order Details].[Order Details$OrderDetails]...
Preparing index Northwind.dbo.[Order Details].[Order Details$OrderID]...
Preparing index Northwind.dbo.[Order Details].[Order Details$OrderStatusLookup]...
Preparing index Northwind.dbo.[Order Details].[Order Details$ProductID]...
Preparing index Northwind.dbo.[Order Details].[Order Details$ProductsOnOrders]...
Preparing index Northwind.dbo.[Order Details].[Order Details$Purchase Order ID]...
Preparing index Northwind.dbo.[Order Details].[Order Details$Status ID]...
Preparing table Northwind.dbo.[Order Details Status]...
Preparing category Triggers of table Northwind.dbo.[Order Details Status]...
Preparing category Indexes of table Northwind.dbo.[Order Details Status]...
Preparing table Northwind.dbo.[Orders]...
Preparing category Triggers of table Northwind.dbo.[Orders]...
Preparing category Indexes of table Northwind.dbo.[Orders]...
Preparing index Northwind.dbo.[Orders].[Orders$CustomerID]...
Preparing index Northwind.dbo.[Orders].[Orders$CustomerOnOrders]...
Preparing index Northwind.dbo.[Orders].[Orders$EmployeeID]...
Preparing index Northwind.dbo.[Orders].[Orders$EmployeesOnOrders]...
Preparing index Northwind.dbo.[Orders].[Orders$ID]...
Preparing index Northwind.dbo.[Orders].[Orders$New_CustomerOnOrders]...
Preparing index Northwind.dbo.[Orders].[Orders$New_EmployeesOnOrders]...
Preparing index Northwind.dbo.[Orders].[Orders$New_OrderStatus]...
Preparing index Northwind.dbo.[Orders].[Orders$New_ShipperOnOrder]...
Preparing index Northwind.dbo.[Orders].[Orders$New_TaxStatusOnOrders]...
Preparing index Northwind.dbo.[Orders].[Orders$OrderStatus]...
Preparing index Northwind.dbo.[Orders].[Orders$ShipperID]...
Preparing index Northwind.dbo.[Orders].[Orders$ShipperOnOrder]...
Preparing index Northwind.dbo.[Orders].[Orders$Status ID]...
Preparing index Northwind.dbo.[Orders].[Orders$TaxStatusOnOrders]...
Preparing index Northwind.dbo.[Orders].[Orders$ZIP/Postal Code]...
Preparing table Northwind.dbo.[Orders Status]...
Preparing category Triggers of table Northwind.dbo.[Orders Status]...
Preparing category Indexes of table Northwind.dbo.[Orders Status]...
Preparing table Northwind.dbo.[Orders Tax Status]...
Preparing category Triggers of table Northwind.dbo.[Orders Tax Status]...
Preparing category Indexes of table Northwind.dbo.[Orders Tax Status]...
Preparing table Northwind.dbo.[Privileges]...
Preparing category Triggers of table Northwind.dbo.[Privileges]...
Preparing category Indexes of table Northwind.dbo.[Privileges]...
Preparing table Northwind.dbo.[Products]...
Preparing category Triggers of table Northwind.dbo.[Products]...
Preparing category Indexes of table Northwind.dbo.[Products]...
Preparing index Northwind.dbo.[Products].[Products$Product Code]...
Preparing table Northwind.dbo.[Purchase Order Details]...
Preparing category Triggers of table Northwind.dbo.[Purchase Order Details]...
Preparing category Indexes of table Northwind.dbo.[Purchase Order Details]...
Preparing index Northwind.dbo.[Purchase Order Details].[Purchase Order Details$ID]...
Preparing index Northwind.dbo.[Purchase Order Details].[Purchase Order Details$Inventory ID]...
Preparing index Northwind.dbo.[Purchase Order Details].[Purchase Order Details$InventoryTransactionsOnPurchaseOrders]...
Preparing index Northwind.dbo.[Purchase Order Details].[Purchase Order Details$New_InventoryTransactionsOnPurchaseOrders]...
Preparing index Northwind.dbo.[Purchase Order Details].[Purchase Order Details$New_ProductOnPurchaseOrderDetails]...
Preparing index Northwind.dbo.[Purchase Order Details].[Purchase Order Details$New_PurchaseOrderDeatilsOnPurchaseOrder]...
Preparing index Northwind.dbo.[Purchase Order Details].[Purchase Order Details$OrderID]...
Preparing index Northwind.dbo.[Purchase Order Details].[Purchase Order Details$ProductID]...
Preparing index Northwind.dbo.[Purchase Order Details].[Purchase Order Details$ProductOnPurchaseOrderDetails]...
Preparing index Northwind.dbo.[Purchase Order Details].[Purchase Order Details$PurchaseOrderDeatilsOnPurchaseOrder]...
Preparing table Northwind.dbo.[Purchase Order Status]...
Preparing category Triggers of table Northwind.dbo.[Purchase Order Status]...
Preparing category Indexes of table Northwind.dbo.[Purchase Order Status]...
Preparing table Northwind.dbo.[Purchase Orders]...
Preparing category Triggers of table Northwind.dbo.[Purchase Orders]...
Preparing category Indexes of table Northwind.dbo.[Purchase Orders]...
Preparing index Northwind.dbo.[Purchase Orders].[Purchase Orders$EmployeesOnPurchaseOrder]...
Preparing index Northwind.dbo.[Purchase Orders].[Purchase Orders$ID]...
Preparing index Northwind.dbo.[Purchase Orders].[Purchase Orders$New_EmployeesOnPurchaseOrder]...
Preparing index Northwind.dbo.[Purchase Orders].[Purchase Orders$New_PurchaseOrderStatusLookup]...
Preparing index Northwind.dbo.[Purchase Orders].[Purchase Orders$New_SuppliersOnPurchaseOrder]...
Preparing index Northwind.dbo.[Purchase Orders].[Purchase Orders$PurchaseOrderStatusLookup]...
Preparing index Northwind.dbo.[Purchase Orders].[Purchase Orders$Status ID]...
Preparing index Northwind.dbo.[Purchase Orders].[Purchase Orders$SupplierID]...
Preparing index Northwind.dbo.[Purchase Orders].[Purchase Orders$SuppliersOnPurchaseOrder]...
Preparing table Northwind.dbo.[Sales Reports]...
Preparing category Triggers of table Northwind.dbo.[Sales Reports]...
Preparing category Indexes of table Northwind.dbo.[Sales Reports]...
Preparing table Northwind.dbo.[Shippers]...
Preparing category Triggers of table Northwind.dbo.[Shippers]...
Preparing category Indexes of table Northwind.dbo.[Shippers]...
Preparing index Northwind.dbo.[Shippers].[Shippers$City]...
Preparing index Northwind.dbo.[Shippers].[Shippers$Company]...
Preparing index Northwind.dbo.[Shippers].[Shippers$First Name]...
Preparing index Northwind.dbo.[Shippers].[Shippers$Last Name]...
Preparing index Northwind.dbo.[Shippers].[Shippers$Postal Code]...
Preparing index Northwind.dbo.[Shippers].[Shippers$State/Province]...
Preparing table Northwind.dbo.[Strings]...
Preparing category Triggers of table Northwind.dbo.[Strings]...
Preparing category Indexes of table Northwind.dbo.[Strings]...
Preparing table Northwind.dbo.[Suppliers]...
Preparing category Triggers of table Northwind.dbo.[Suppliers]...
Preparing category Indexes of table Northwind.dbo.[Suppliers]...
Preparing index Northwind.dbo.[Suppliers].[Suppliers$City]...
Preparing index Northwind.dbo.[Suppliers].[Suppliers$Company]...
Preparing index Northwind.dbo.[Suppliers].[Suppliers$First Name]...
Preparing index Northwind.dbo.[Suppliers].[Suppliers$Last Name]...
Preparing index Northwind.dbo.[Suppliers].[Suppliers$Postal Code]...
Preparing index Northwind.dbo.[Suppliers].[Suppliers$State/Province]...
Synchronization operation was canceled by user.
Load operation is complete.
Migrating data...
Analyzing metadata...
Data migration operation has finished.
0 table(s) successfully migrated.
0 table(s) partially migrated.
0 table(s) failed to migrate.
Operation canceled.












Friday, April 15, 2011

Upsize Microsoft Access Databases to SQL Azure with SSMA 4.2

Bill Ramos explained Migrating Access Jet Databases to SQL Azure in a 4/14/2011 post:

image In this blog, I’ll describe how to use SSMA for Access to convert your Jet database for your Microsoft Access solution to SQL Azure. This blog builds on Access to SQL Server Migration: How to Use SSMA using the Access Northwind 2007 template. The blog also assumes that you have a SQL Azure account setup and that you have configured firewall access for your system as described in the blog post Migrating from MySQL to SQL Azure Using SSMA.

Creating a Schema on SQL Azure

imageIf you are using a trial version of SQL Azure, you’ll want to get the most out of your free 1 GB Web Edition database. By using a SQL Server schema, you can accommodate multiple Jet database or MySQL migrations into a single database and limit access to users for each schema via the SQL Server permissions hierarchy.

SSMA for Microsoft Access version 4.2 doesn’t support the creation of a database schema within the tool, so you will need to create the schema using the Windows Azure Portal. Launch the Windows Azure Portal with your Live ID and follow the steps as shown below.

01 Windows Azure Portal

  1. Click on the Database node in the left hand navigation pane.
  2. Expand out the subscription name for your Azure account until you see your databases
  3. Select the target database that you created when you first connected to the Azure portal – see Migrating from MySQL to SQL Azure Using SSMA for how the SSMADB was created for this blog.
  4. Click on the Manage command to launch the Database Manager. You will log in into SQL Azure database as shown below.
    02 Login to DB Manager

Once in the Database Manager, you will need to press the New Query command as shown below so that you can create the target schema for the Northwind2007 database.

03 Create new query in DB Manager

Now that you have the new query window, you can do the following steps as illustrated below.

04 issue create schema command

  1. Type in the Transact-SQL command to create your target schema: create schema Northwind2007
  2. Press the Execute command in the toolbar to run the statement.
  3. Click on the Message window command to show that the command was completed successfully.

You are now ready to use SSMA for Access to migrate your database to SQL Azure into the Northwind2007 schema.

Creating a Migration Project with SQL Azure as the Destination

Start SSMA for Access as usual, but close the Migration Wizard that starts by default. The Migration Wizard will end up creating the tables in the dbo schema instead of the Northwind2007 schema that you created. Follow the steps shown below to create your manual migration project.

10 Create new project

  1. Click on the New Project command.
  2. Enter in the name of your project.
  3. Select SQL Azure for the Migration To option and click OK. If you forget to select SQL Azure, you’ll need to create a new project again because you can’t change the option once you have competed the dialog.

The next step is to add the Northwind2007 database file to the project and connect to your SQL Azure database as shown below.

11 Add databases and connect to SQL Azure

  1. Click on the Add Databases command and select the Northwind2007 database.
  2. Expand the Access-metadata node in the Access Metadata Explorer to show the Queries and Tables nodes and select the Tables checkbox.
  3. Click on the Connect to SQL Azure command
  4. Complete the connection dialog to your SQL Azure database
Choosing the Target Schema

To change the target schema, you need to Modify the default value from master.dbo to database name and schema that you created for your SQL Azure database – in this example – SSMADB.Northwind2007 following the steps below.

12 Cloosing the schema

  1. Click on the Modify button in the Schema tab.
  2. Click on the […] brose button in the Choose Target Schema dialog.
  3. Choose the target schema – Northwind2007 - and then click the Select and the OK button.
Migrate the Tables and Data with the Convert, Load, and Migrate Command

At this point, you are ready to proceed with the standard migration steps for SSMA which includes (ignoring errors):

  1. Click on the Tables folder for the Northwind2007 database in the Access Metadata Explorer to enable the migration toolbar commands.
  2. Click on the Convert, Load, and Migrate command to do all the steps to compete the migration with the one command.
  3. Click OK for the Synchronize with the Database dialog as shown below to create the tables in the Northwind2007 schema within the SSMADB database.
    13 Sync tables to target
  4. Dismiss the Convert, Load, and Migrate dialog assuming everything worked.
Using SSMA to Verify the Migration Result

To verify the results, you can use the Access and SQL Azure Metadata Explorers to compare data after the transfer as follows.

14 Verify the results

  1. Click on the source table Employees in the Access Metadata Explorer
  2. Select the Data tab in the Access workspace to see the data
  3. Click on the target table Employees in the SQL Azure Metadata Explorer
  4. Select the Table tab in the SQL Azure workspace to see the schema or the Data tab to view the data.

You can also use the SQL Azure Database Manager to view the table schema and data as described at the end of the blog post Migrating from MySQL to SQL Azure Using SSMA.

Creating Linked Tables to SQL Azure for your Access Solution

To make your Access solution use the SQL Azure tables, you need to create Linked tables to the SQL Azure database. To create the Linked tables, you need to select the Tables folder in the Access Metadata Explorer as shown below.

15 Link Tables

Right click on the Tables folder and select the Linked Tables command. SSMA will create a backup of the tables in your Access solution file and then create the Linked Table that connects to the table in SQL Azure.

Summary

As you can see, migrating your Access solution that uses Jet tables as easy as:

  1. Creating a target schema in your target SQL Azure database.
  2. Creating a project with the Migrate To option set to SQL Azure.
  3. Following the normal steps for migrating schema and data within SSMA.
  4. Verifying the reports within SSMA or through the SQL Azure Database Manager.
  5. Creating Linked Tables to the SQL Azure database within your Access solution using SSMA.

Additional SQL Azure Resources

To learn more about SQL Azure, see the following resources.

Monday, March 28, 2011

Microsoft Offered Updated Office 365 Beta Service Descriptions on 3/21/2011

The Microsoft Download Service offered the following *.docx files for download on 3/21/2011 with no fanfare:

These documents provide a detailed description of the features and functionality of Office 365 services currently in beta.

File Name: Size: Download
Microsoft_Exchange_Online_Beta_Service_Description.docx 2.1MB Download
Microsoft_Lync_Online__Beta_Service_Description_Final.docx 137KB Download
Microsoft_Office_Professional_Plus_Beta_Service_Description_Final.docx 924KB Download
Microsoft_Office_Web_Apps_Beta_Service_Description_Final.docx 185KB Download
Microsoft_SharePoint_Online_Standard_Beta_Service_Description_Final_ Mar2011-update.docx 2.5MB Download
Office 365 Beta Enterprise Support Service Description_Final.docx 385KB Download
Office_365_Beta_Identity_Service_Description_final.docx 335KB Download
Office_365_Security_Service_Description_Final.docx 550KB

Download

imageOf course, what most folks want is details of the “features and functionality of Office 365 services” to be in the released product.

According to the “Microsoft SharePoint Online Beta Service Description” document, Access Services will be available in the following User Subscriptions:

  • image For Small Businesses SharePoint Online in Plan P1
  • For Information Workers SharePoint Online Plan 2 in E3/E4

Kurt Mackie Described Office 365 Licensing in a RedmondMag.com Article of 3/26/2011

Office 365 Licensing: Analyst Explains All

Licensing Office 365 was the topic of a Directions on Microsoft talk last week, which may be of interest to IT pros, especially since Microsoft is preparing to launch those services sometime this year.

Availability of Office 365 may be just around the corner. In response to a question during the online session last Thursday, Rob Horwitz, research chair at the Directions on Microsoft consultancy, said that Microsoft intends to deliver Office 365 commercially "before July 2011." However, he noted that Microsoft hasn't publicly announced the start date.

Understanding Office 365 licensing doesn't require a slide rule, an advanced computer science degree or a Microsoft certification, but it probably does require expert advice (and maybe you'll want to keep a lawyer on retainer). During the talk, Horwitz sketched out the major licensing information forks to consider amid a preponderance of choices.

Office 365, like the Business Productivity Online Suite (BPOS) it will succeed, will be offered via monthly recurring subscription fees on a per-user basis. Subscriptions will be available via Microsoft's online subscription program or through enterprise agreements (EAs) with Microsoft. Subscriptions will also be available from Microsoft's partners. The EA route enables better discounts, Horwitz said, and most organizations will likely buy Office 365 through that means. If an organization doesn't have an EA in place, one can be started principally to run Office 365, he added. Office 365 isn't available through Select or Select Plus or open subscription licensing, he explained.

Organizations used to licensing on-premises Microsoft solutions through EAs will have some licensing complications to consider if they migrate to Office 365. For those already using Microsoft's BPOS online services, a helpful Microsoft blog post indicates that current BPOS customers will have a year to opt into Office 365, but those who delay their move won't get all of the benefits of the new suite of services. BPOS users considering moving to Office 365 can get more information at Microsoft's Office 365 transition center page.

Bundled Online Offering
Office 365, when available, will offer a bundle of services based on four of Microsoft's on-premises products. Organizations will get automatic software updates through the service, but Office 365 services currently don't have all of the features offered by the on-premises products. The one standout included in the offering is Office Professional Plus, which is a premises-installed software product. Horwitz said that organizations subscribing to Office 365 would likely be responsible for having to maintain Office Professional Plus themselves, including patching and upgrades.

The four services in Office 365 are as follows:

  • Exchange Online 2010
  • Lync Online 2010
  • SharePoint Online 2010, and
  • Hosted Web Apps

Horwitz noted that the Web Apps, which include Word, Excel, PowerPoint and OneNote, have some limitations when compared with their on-premises cousins. For instance, macros don't work in Excel, he said. Moreover, Office Web Apps can only open documents on a SharePoint site.

Microsoft supports mixed use of on-premises products and services in a hybrid approach. Horwitz said that Exchange Online offers the greatest parity with the on-premises Exchange product. The exceptions include no support for public folders with Exchange Online, plus organizations cannot use Outlook 2003 as a client app for e-mail.

Microsoft's blog post flatly declares that Office 365 does not support "Windows 2003 or earlier, Microsoft Office 2003 and Microsoft Office Outlook 2003." In addition, there is no support for Internet Explorer 6, so those organizations with Web apps built on that browser face some choices if moving to Office 365.

Lync Online has some limitations, Horwitz said. It can't be used for call control of a PBX (private branch exchange). It has limited federation capabilities with non-Microsoft solutions. In addition, users currently can't make or receive calls to or from public switched telephone network (PSTN) users.

SharePoint Online has limited integration with existing business systems, Horwitz explained. It has limited compatibility for scorecards or dashboards, he added.

Licensing Dice and Slice
Office 365 licensees will have about a dozen options from a "dice and slice" menu designed to support small businesses, medium-size businesses and deskless workers (now called "kiosk workers" in Microsoft's licensing parlance), Horwitz explained.

Small business users are defined as having up to 25 users at $6 per user per month. There's no support for more than 50 mailboxes, and no support for conferencing with more than 50 users.

Microsoft has four licensing categories for enterprises (E1 through E4), which are nested "like Russian dolls," with E4 being the most inclusive offering, Horwitz explained. These options include Exchange Online e-mail support for mailboxes of 25 GB in size, personal archiving, calendar and contacts.

The E-1 license includes all Office 365 features at $10 per user per month. The E-2 license adds to that by allowing the editing of documents at $16 per user per month. The E-3 license tops the other two by adding voicemail capability at $24 per user per month. Lastly, the E-4 license adds telephony capabilities at $27 per user per month, such as the ability to make or receive PSTN calls -- although Horwitz said this capability will come later. Even when this capability is available, a "special PSTN number" will be required to make it work, he noted.

The above prices apparently are estimates, and Microsoft could change them by the time it releases Office 365. Microsoft did release its own description of Office 365 pricing that is less detailed than Horwitz's description. Microsoft's pricing list settles on a $24 per user per month price for "organizations who want Office Professional Plus desktop software along with the full functionality of Exchange, SharePoint and Lync Online." This pricing description can be accessed here (Word doc download) from Microsoft's Office 365 home page.

Licensing Overlap
Organizations that already have an EA in place will likely experience "licensing overlap" with Microsoft Office, Horwitz said. Microsoft will allow its EA customers to switch their core Client Access Licenses (CALs) for something called the "Enterprise CAL Suite Bridge for Office 365," which will lower their costs.

The Enterprise CAL Suite Bridge option will only be available to organizations that have an organization-wide EA in place. Microsoft will have the customer sign a contract amendment for the CAL Suite Bridge. This licensing change won't be allowed during the first year. It's not until the next anniversary of the EA, called the "true-up" time, that organizations will be able to get the less expensive CAL Suite Bridge option, Horwitz explained.

Microsoft's licensing is fairly complex, even after an explanation. One possible remedy for further clarification is to attend a Directions on Microsoft event. The consultancy plans to offer its next "Licensing Boot Camp" on April 19 and 20 in Las Vegas, with other dates to follow. The talk by Horwitz can be accessed here.

Notice that there’s no mention of Access Services, Excel Services or InfoPath services in the article.


Tuesday, March 22, 2011

SharePoint 2010 Lists’ OData Content Created by Access Services is Incompatible with ADO.NET Data Services

Updated 3/21/2011 with Pablo Castro’s reply of 3/21/2011 to my thread about the problem in the OData Mailing List (see end of post).

Updated 3/20/2011 with added introductory background material and links to related information.

Introduction

image Microsoft SharePoint has gained a substantial share of the market for content management and collaboration tools. Sales of SharePoint 2007 exceeded US$1 billion and Mary Jo Foley reported in her What Is Microsoft's Next Billion-Dollar Business? article of 9/1/2010 for Redmond Magazine that “SharePoint is well on its way to becoming Microsoft's first new $2 billion business.”

image SharePoint 2010 is likely to become a data source for a wider range of Microsoft .NET, Windows Phone 7 and other OS client applications because it it exposes list collections in OData format. My Access Web Databases on AccessHosting.com: What is OData and Why Should I Care? post of 3/16/2011 explains the significance of OData-formatted information and how to manipulate it with PowerPivot for Excel.

image Microsoft Access 2010 has the capability to easily and quickly publish conventional *.accdb databases to Web Databases, which run under SharePoint 2010’s Access Services. Access Services stores relational tables in SharePoint lists, displays forms in SharePoint Web pages, and prints reports with the assistance of SQL Server Reporting Services.

image Visual Studio LightSwitch Beta 2 is a rapid application delivery (RAD) framework for SilverLight Windows and Web database clients that targets user and targets developer populations similar to those of Access. LightSwitch accepts OData, SQL Server, and SQL Azure as a data sources. PowerPivot for Excel runs on OData from SharePoint, and OData’s the only data format offered by Microsoft’s Windows Azure Marketplace DataMarket.

image Windows Phone 7 has an OData software development kit (SDK), Android phones can process OData with the Java SDK, and there’s an OData SDK for iPhone’s Object C language. (See J. C. Cimetiere’s OData interoperability with .NET, Java, PHP, iPhone and more post of 3/16/2011 to the Interoperability @ Microsoft blog.) OData is likely to become a leading format in the rapidly growing mobile data market.

Problem Discovery

While running tests with SharePoint 2010’s OData producer as a data source for Visual Studio 2010 and LightSwitch Beta 2 client applications, I encountered the following error when attempting create a Visual Studio LightSwitch Beta 2 Service Reference from an Access application published to SharePoint 2010:

1. I started a LightSwitch project in Visual Studio and selected SharePoint as the Data Source Type:

SP2010ODataVSLSDataSource575px

2. I clicked Next to Enter Connection Information for a SharePoint site created from an Access 2010 project:

SP2010ODataVSLS_AHSignOn575px

The NorthwindTraders site was created by running the Northwind Traders Web Database template from Office Online to create an Access *.accdb database and then publishing it to Access Services in a hosted SharePoint 2010 instance at AccessHosting.com.

3. When I clicked Next, I received the following error message:

SP2010ODataVSLS_AH_OldID575px

The problem relates to the OData client rejection of two leading underscores in the Name property of a column in all lists generated by Access tables. However, the Microsoft SQL Server Data Portability specification for Simple Identifier provides the following specification:

2.2.4 SimpleIdentifier

The SimpleIdentifier attribute specifies an identifier that conforms to the rules for the String data type as specified in [XMLSCHEMA2].

The following is the XML schema definition of the SimpleIdentifier attribute.

<xs:simpleType name="TSimpleIdentifier">
<xs:restriction base="xs:string"/>
</xs:simpleType>

The XML Schema Character Range for Char is: 


Char
   ::=  
#x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF]
/* any Unicode character, excluding the surrogate blocks, FFFE, and FFFF. */


The preceding specifications don’t appear to me to specify a pattern that precludes two leading underscores.


You can’t edit the column name of a list linked to Access in the SharePoint UI or with SharePoint Designer 2010. The field is hidden by default in Access Datasheet view. You can unhide the field, but Datasheet views of tables linked to SharePoint lists don’t have a Design mode:


SP2010ODataVSLS_AH_OldIDinAccess1024px


To change the __OldID column name to OldID, you must disconnect the Access front-end from the Access Services version to enable modifying the list designs in the UI, edit 15 lists for this example, and then reconnect Office Access to Access Services. This is, to be generous, a daunting task.


After you perform the preceding tasks for the NorthwindTraders example, the Choose Your SharePoint Items dialog appears as expected:


image


Following is the corrected Product entity displayed in VS LightSwitch Beta 2:


SP2010ODataProductsInVSProj1024px


So far, I haven’t found any side effects from removing the two underscores, other than the OldID column now appears by default in Access Datasheet view.


Tests with a simple VS 2010 C# Console application exhibit the same problem.


image It’s interesting that PowerPivot for Excel doesn’t exhibit a similar problem. See the “Browsing OData-formatted Web Database Content in PowerPivot for Excel” section of my Access Web Databases on AccessHosting.com: What is OData and Why Should I Care? post.


Conclusion


The pattern applied to the TSimpleIdentifier Entity Data Model data type that precludes leading underscores should be removed in a later EDM v4.1 CTP because the rule is arbitrary. Changes to Access Services to eliminate the leading underscore and change the method for making columns with such names hidden by default in Access would need to wait for Office Service Pack 2.


Update 3/22/2011 Pablo Castro’s reply of 3/21/2011 to my thread about the problem the OData Mailing List:


Date: Mon, 21 Mar 2011 05:54:35 +0000

image From: Pablo Castro <Pablo.Castro@MICROSOFT.COM>

Subject: Re: ADO.NET Data Services Client Considers Field Names with Leading Underscores Invalid

I pinged the SharePoint folks to see if this is a known issue and whether there are any workarounds. The short story is that there is a mismatch of rules between SharePoint names and EDM names, so the adapter between the two needs to deal with these things. If I hear from them I'll get back to this thread with whatever I learn.

-pablo

Pablo is a Microsoft Software Architect and OData’s initial Program Manager and Technical Lead. If Pablo replies, I’ll post an update.


Full Disclosure: I’m a contributing editor for Visual Studio Magazine, a sister publication to Redmond Magazine, both published by 1105 Media.



Sunday, March 20, 2011

Access to SQL Server Migration: Access Solutions using SQL Server

Bill Ramos (@billramo) posted Mary Chipman’s (@marychipman) Access to SQL Server Migration: Access Solutions using SQL Server, Part 1 and Access to SQL Server Migration: Access Solutions using SQL Server, Part 2 on 3/19/2011. From Part 1’s introduction:

image In Part 1 and Part 2 I’ll discuss your options for continuing to use Access as a front-end client once you have migrated the data to SQL Server. Some people come to SQL Server migration as Access developers who are new to SQL Server, whereas others may be IT professionals who know little about Access, so I will attempt to bridge any gaps with useful information for everyone. The SSMA Migration Assistant for Access (SSMA) makes it easy to link converted SQL Server tables and queries to the Access database you started from. For applications of any complexity, migrating the data is by far the easiest step. If your existing Access application suffered from intractable problems when the tables were in native Jet/ACE format, and you have done nothing to fix or at least understand those problems, then you are most likely going to have even bigger problems with SQL Server.

image The Access client application has often been dismissed as a "toy" because of its ease of use, but when understood and used appropriately with SQL Server on the back end, those very features can help you quickly deliver cost-effective results with a low TCO. Access is not a suitable client for Web or n-tier applications that require a separate data access layer, although it can be used in conjunction with other clients, such as ASP.NET. There are always tradeoffs involved between ease of development, efficiency and security when using Access in a 2-tier, client-server scenario. You will need to determine which of the following techniques are best suited to your needs.

From Part 2’s introduction:

image In Part 2 I'll continue the discussion about how you can "tread lightly" on your SQL Server by making your Access front end an efficient and economical data consumer. I'll focus on techniques you can use to keep your application running efficiently, freeing up network and server resources in the process.

Mary is an independent consultant, an Access security expert, and a former developer/writer for the Microsoft Access team. She’s co-author of the classic Microsoft Access Developer's Guide to SQL Server.

Friday, March 18, 2011

Upsizing the Northwind Web Database to an Updated SharePoint 2010 Server Hosted by AccessHosting.com

Updated 3/18/2011 with instructions for correcting time-zone errors starting at Figure 7.

image Chapter 23 of my Microsoft Access 2010 In Depth book, “Sharing Web Databases with SharePoint Server 2010,” includes a “Signing Up for and Testing a Trial Access Hosting Account” section. After the book published, AccessHosting.com upgraded their shared hosting plan in January 2011 with the following new features:

    • Support for English, Spanish, German, and French language packs on shared hosting plans …
    • Support for the OData service entry point into all Access Web Databases (see my What is OData and Why Should I Care? post of 3/12/2011.)
    • A new and improved control panel for self-service administration of user account passwords
    • Support for permissive handling of all file types including PDF
    • Support for SharePoint Designer outside of Access Web Databases

I was interested in giving SharePoint’s Open Data Protocol (OData) Service a try, so I requested and received an upgrade to my Access Hosting test account. To simplify the initial testing of OData representation of data delivered by SharePoint Server’s Access Services, I downloaded the Northwind Traders Web Database template from Office Online to create a local NorthwindWebDatabase.accdb (NWWDB) Access 2010 database.

NWWDB is an extensively revised version of the classic Northwind.mdb, which has been Access’s sample database file since v1.0’s “Cirrus” beta. To simplify browser-based data entry and editing, NWWDB uses Access 2010’s new Navigation (tab) control to choose data entry pages. For example, here’s a screen capture of the Products List page:

imageFigure 1.

SharePoint lists don’t support relationships, so Category is a lookup field that lets you select from a list populated by the Categories table. Similarly the Supplier lookup field is populated by the Suppliers table.

Clicking the File tab’s Info link opens the Information page:

imageFigure 2.

Clicking the Publish to Access Services button runs the Compatibility Checker and opens the Save & Publish page:

imageFigure 3.

Typing the Server URL (http://oakleaf.accesshosters.com for the updated shared hosting servers) generates the full URL for uploading to a specific site (http://oakleaf.accesshoster.com/NorthwindTraders.)

Clicking the Publish to Access Services button connects to your account at AccessHosting’s Website and display the Windows Security dialog:

imageFigure 4.

Typing an administrative password and clicking OK starts the upload process, which displays a progress dialog for each table, form and report:

image

imageFigure 5.
After a couple of minutes or more, depending on your upload bandwidth, the following success dialog opens:

imageFigure 6.

Click OK to dismiss the dialog, open IE and navigate to the full URL (http://oakleaf.accesshoster.com/NorthwindTraders for this example) to display the default Dashboard form for entering new orders. (If you didn’t mark the Save My Credentials check box in the login dialog above, you’ll need to log in.)

If you local time zone isn’t Eastern, which is SharePoint’s default and the location of Access Hosting (Delaware), you receive a warning at the top of the screen:

image

Figure 7.

Click the More Information link, which leads to a generic Fix a Technical Problem page, close the page, click the Options menu, choose Site Permissions to open the Permission Tools ribbon, open the Site Actions menu, and choose Site Settings to open the Site Settings page and click the Site Administration group‘s Regional Setting link:

image

Figure 8.

image

Figure 9.
In the Regional Settings page, select your Time Zone from the list:

image

Figure 10.

Scroll down and click OK to save your change.
Return to the Dashboard and click the Products tab to open SharePoint’s version of Figure 1:

imageFigure 11.

Pasta is obviously the wrong category for Chai (according to Wikipedia, A beverage made with black teas, steamed milk and sweet spices based loosely on Indian recipes), so open the Category field’s lookup list and select Beverages:

imageFigure 12.

Click the selection button of another record in the leftmost column of the grid to save the Category change.

Display NorthwindTraders Content as OData in IE9

Navigate to http://accountname.accesshoster.com/sitename/_vti_bin/listdata.svc (http://oakleaf.accesshoster.com/NorthwindTraders/_vti_bin/listdata.svc for this example) to display the chosen site’s lists available as OData collections:

imageFigure 13.

Note: The “vti” element of the_vti_bin folder name is an abbreviation for Vermeer Technologies, Inc., the original developers of the FrontPage Web designer for Internet Explorer. Microsoft purchased the FrontPage code in January 1966 and then discontinued the product in 2006 in favor of Microsoft SharePoint Designer and Microsoft Expression Web.

Viewing the contents of collections requires turning off IE9’s Feed Reading view, which is enabled by default. To do this, click the Tools icon, choose Internet Options to open the dialog of the same name, click the Content tab and Feeds and Web Slice Setting button to open the dialog of the same name, and clear the Turn On Feed Reading View check box:

imageFigure 14.

Click OK twice to close the dialogs and save your changes.

Reopen IE and navigate to http://sitename.accesshoster.com/sitename/_vti_bin/listdata.svc/listname (http://oakleaf.accesshoster.com/NorthwindTraders/_vti_bin/listdata.svc/Products for this example) to display the content of collections exposed by SharePoint 2010. To display a member of the collection by its ordinal, add the number as a suffix enclosed in parentheses (http://oakleaf.accesshoster.com/NorthwindTraders/_vti_bin/listdata.svc/Products(1) for this example):

imageFigure 15.

Note: Item names contained in OData query expressions, such as Products in the preceding URL example, are case-sensitive. The Edm type prefix is an abbreviation for Entity Data Model, which describes data types compatible with the ADO.NET Team’s Entity Framework v4.1.

See my What is OData and Why Should I Care? post of 3/12/2011 (updated 3/17/2011) for more information about OData and manipulating OData-encoded lists with Microsoft Power Pivot for Excel 2010.