Differences

This shows you the differences between two versions of the page.

--- dynamiczip:faq:dynamiczip_accomodate_migrations_to_sql_server_faq [2015/03/05 19:15] – external edit 127.0.0.1
+++ dynamiczip:faq:dynamiczip_accomodate_migrations_to_sql_server_faq [2017/09/08 16:49] (current) – conni
@@ Line 1: / Line 1: @@
 ======How does DynamicZip accommodate migrations to Microsoft SQL Server? ======
-**NOTE:** The following applies to migrations from other databases such as Btrieve or c-tree to Microsoft>> SQL Server. It does not apply to upgrades from one version to another on Microsoft SQL Server.
+**NOTE:** The following applies to migrations from other databases such as Btrieve or c-tree to Microsoft >> SQL Server. It does not apply to upgrades from one version to another on Microsoft SQL Server.
-**IMPORTANT:**
-  * Prior to importing the ZIPsales Database in the new installation, verify that your [[dynamiczip:windows:DynamicZip Setup window]] for the new installation agrees with your setup options for the old installation. The DynamicZip Setup window's section on Import Settings is particularly important. For example, if the old installation did not use naming rules for new cities and counties and the new installation does, the [[dynamiczip:windows:dz_tax_detail_supplement_window|Tax Detail Supplement]] record may not get created for certain tax details that exist on posted transactions. If this does happen, then the missing tax detail supplement records can be manually created in the new system. Alternately, you can print reports on anything prior to the upgrade by keeping a working copy of the old system.
-  * If you utilize the DynamicZip [[dynamiczip:features:Purchase Tax Accrual]] feature, then you will need to have the DZ PM Taxes Work and History table (DZ10500) converted from Pervasive to Microsoft SQL Server. If this is the case, then please [[kampdata:Contact Us]].
+**IMPORTANT:** Prior to importing the ZIPsales Database in the new installation, verify that your [[dynamiczip:windows:DynamicZip Setup window]] for the new installation agrees with your setup options for the old installation. The DynamicZip Setup window's section on Import Settings is particularly important. For example, if the old installation did not use naming rules for new cities and counties and the new installation does, the [[dynamiczip:windows:dz_tax_detail_supplement_window|Tax Detail Supplement]] record may not get created for certain tax details that exist on posted transactions. If this does happen, then the missing tax detail supplement records can be manually created in the new system. Alternately, you can print reports on anything prior to the upgrade by keeping a working copy of the old system.
 DynamicZip creates and manages several tables that, depending on which states you are collecting tax in and your DynamicZip setup options, can be quite large (100+ MB per company). These large tables include the Sales/Purchase Tax Master table group in Microsoft Dynamics GP This table group is comprised of standard Microsoft Dynamics GP tables and as such will be included in your migration.