My MSSQL Dataset Migration failed... . Now what do I do?

Problem

How to re-migate a PSQL dataset to MSSQL when the MSSQL migration failed

From a customer  "I received several MSSQL errors during migration and AGRIS program crashed and would not launch. I then stopped the PSQL services and copied the dataset back from backup. I'm able to launch Agris and select other dataset but I'm unable to select the failed dataset or migrate it again."

Solution

Recovering from a failed migration is not a situation any of us want. 

If you did not sign up for the Greenstone MSSQL migration service here are the high level tasks to attempt a recovery process. 

High level tasks 

1. Add a new psql dataset.
2. Copy the psql data into the dataset,
3. Validate the dataset within AGRIS.
4. Rebuild any missing files or files with bad record lengths.
5. Go to dataset maintenence and then select the newly created psql dataset and migrate again...(please remember - only do this step only after validating the psql dataset)
   
   

Related articles

• Page:
  MSSQL Server and Client Configuration Recommendations and Requirements
• Page:
  How to remove MSSQL records associated with a failed dataset migration or dataset copy - Generate Delete Data from All Tables by TenantID
• Page:
  MSSQL How To find the active connections to the database. (system or users)
• Page:
  MSSQL Transaction Timeout and Rollback
• Page:
  MSSQL Maximum server memory setting - How do I determine if MSSQL is using too much memory or storage space?