Dynamics Gp Data Recovery And Repair

Traditionally Great Plains architecture doesnt have three tiers and complete application server is missing

. There are elements of app server as you can outsource batch posting to another computer. But we cannot say that such SQL features as transaction commit and rollback are deployed at their full functionality. Of course good strategy is to restore company database from backup. But in such situation you may lose documents entered in other modules and we also saw situation when backup stopped working several month ago and IT support person had no idea about this fact. Lets review the reasons for the records to become corrupt and repair techniques:

1.Data corruption causes. Batch posting interruption. The most popular is when you trigger batch for posting and your computer crushes due power outage or due to the fact that too many applications are open at the same time and processor and memory are overloaded. When posting is aborted it doesnt necessary mean that data is screwed. There is batch recovery process and you just need to read manual. If you see the message that editing is required then likely you do not have one or more GL accounts in documents distribution and this problem could be reviewed by printing Batch Edit List report with following transaction editing. However there are situations when SQL level repair is required. Lets think about the sequence of processes in posting. When you initiate the process all the documents are checked on their consistency. If you got issues as we described above with distribution accounts then you are lucky. Next step process is moving documents all the level down to General Ledger. If power outage occurred during that phase then the situation might be messed up. Try batch recovery and check links and if they do not help then you need to think about fixing in SQL

2.Buggy Customization. This scenario is popular as even experienced Dexterity programmer makes mistakes and there is not much budget to allow full scale Quality Assurance if your customization is unique and coded for your company only. Good recommendation is to maintain testing server where your Dynamics and company database images are loaded from production backup and where Dexterity is installed for the purposes of debugging. Test server could help you catch software bugs and by doing so illuminate the problem in the future

3.SQL Stored Procedure level integration with external database. Microsoft SQL Server is a great tool but it is powerful and at the same time it doesnt validate GP business logic. For example if you issue the query delete RM00101 and execute it in Query designer then all your customers will be deleted. We strongly recommend you to use eConnect and program integration in Microsoft Visual Studio C# or VB projects. eConnect SDK (Software Development Kit) respects business logic and it should prevent software developers from accidental data corruption. If you need to feed data to Dynamics from external application hosted in Linux with MySQL database on PHP platform then consider creation SOAP XML Web Service in Visual Studio with eConnect libraries and call it from Linux PHP application

4.Dealing with corrupted records. First of all you need to identify the table. Please review table structure: Tools -> Resource Description -> Tables. Then via SQL select statement figure out if corrupt documents is in. Next we usually backup the table: Select * into SOP10100_Copy from SOP10100 this query will copy Sales Documents Header table. Then you do data repair (usually with SQL Update or Delete statements). If you did more harm then simply reload the table (drop DEX_ROW_ID column first in our case from SOP10100_Copy table)

Lets answer some popular questions:

Q. If we are on legacy Great Plains 7.5 on Pervasive SQL Server 2000 then what are the options to access database?

A. You need to produce DDF files first. Please see DDF manual. Then you create company ODBC connection in Pervasive SQL Control Center. We usually recommend Microsoft Access for data repair itself but you can try to do the job in Control Center itself

Q. Our old GP SQL Server crushed and we have to move databases to new server hardware. We restored all the databases and remapped ODBC connection in GP login. However since then only sa user can login to the system. What went wrong?

A. GP has users as a layer above SQL Server logins. You need to transfer security from the old SQL Server to the new one. Alternatively take a look at knowledge base as there is the article on how to transfer GP server from one computer to another

For additional information please call us: 1-866-528-0577, 1-630-961-5918 or email us: help@albaspectrum.com

by: Andrew Karasev

POST COMMENT

What To Look In Real Estate Agents Before Buying And Selling Irvine Homes? Jobst Compression Stockings And Regular Socks Wind Turbine Prices Are Low Right Now And Here Is Why Bloated Up Myths About Bankruptcy And Their Concrete Facts Fitness Recommendations To Help You Get Up And Relocating! Black Magic And Spell Curse Banishing Cyberlocker And File Hosting Sites - Get Paid To Upload Phone Psychic And Spirit Guidance Website Design Example And Print Brochure - The Benefits Health And Nutrition Premiere Website-minerva Place Worldwide Shower As Well As Body Functions Products And Discount Coupons For You Creative And Modern Office Design Space Analysis And Workstation Requirements