User Tools

Site Tools


dynamiczip:install:mods:release:build72:sql_optimized_import

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
dynamiczip:install:mods:release:build72:sql_optimized_import [2015/12/14 23:04] chuckdynamiczip:install:mods:release:build72:sql_optimized_import [2021/10/27 16:29] – [Access Denied] chuck
Line 6: Line 6:
 In order for BULK INSERT to function properly:  In order for BULK INSERT to function properly: 
   * The [[dynamiczip:glossary:rate_and_boundary_database|Rate & Boundary Database]] must be located on a local drive on the SQL Server machine.   * The [[dynamiczip:glossary:rate_and_boundary_database|Rate & Boundary Database]] must be located on a local drive on the SQL Server machine.
-  * The [[dynamiczip:features:import:rate_and_boundary_import|Rate & Boundary Import]] [[dynamiczip:glossary:path_on_server|Path on Server]] must be properly set.+  * The  [[dynamiczip:glossary:path_on_server|Path on Server]] must be properly set in the [[dynamiczip:windows:dz_rate_and_boundary_import_window|DZ Rate And Boundary Import window]].
   * The user running the import must be assigned the bulkadmin Server Role for the SQL Server. This roll must be assigned to the Microsoft Dynamics GP user's login ID.   * The user running the import must be assigned the bulkadmin Server Role for the SQL Server. This roll must be assigned to the Microsoft Dynamics GP user's login ID.
  
 **IMPORTANT:** If BULK INSERT fails, the [[dynamiczip:glossary:rate_and_boundary_database|Rate & Boundary Database]] files will be read in the traditional (and slower) way. Failure of the BULK INSERT process will __not__ slow down the other import process that have been optimized.  **IMPORTANT:** If BULK INSERT fails, the [[dynamiczip:glossary:rate_and_boundary_database|Rate & Boundary Database]] files will be read in the traditional (and slower) way. Failure of the BULK INSERT process will __not__ slow down the other import process that have been optimized. 
  
-Although maintaining two versions will be extra work, we believe it will be a great way for us to catch errors in the import process. The Non-Optimized Import also provides our users with an alternative way to perform the  [[dynamiczip:features:import:rate_and_boundary_import|Rate & Boundary Import]] should the SQL Optimized Import fail for any reason. +The Non-Optimized Import provides our users with an alternative way to perform the  [[dynamiczip:features:import:rate_and_boundary_import|Rate & Boundary Import]] should the SQL Optimized Import fail for any reason. 
  
 +===== Access Denied =====
 +The error message indicating that the import file cannot be opened such as:
 +<code/>
 +Cannot bulk load because the file FipsCodes.txt could not be opened. Operating system error code 5(Access is denied
 +</code>
 +seems to typically be related to the security context under which the SQL Server service is running. Switching the SQL Server login to Local System Account may eliminate the error. 
 ---- ----
  
 [[dynamiczip:install:mods:modifications|Modifications]] [[dynamiczip:install:mods:modifications|Modifications]]
dynamiczip/install/mods/release/build72/sql_optimized_import.txt · Last modified: 2021/10/27 16:29 by chuck

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki