MSSQL and PSQL running at the same time? Can I do that?

Curious how to move forward to the MSSQL version of AGRIS?  Here is a question posed by a customer just like you. 

"We are concerned about the Hard Drive space required for MSSQL to migrate all of the historical datasets. Is there a way to bring our production dataset forward to MSSQL and keep the historical datasets on PSQL?"

Answer:

Yes this is possible to an extent.   But ultimately will require a higher level of I.T. management to be successful.  

Here are some pointers and tips. 

1. MSSQL can operate to manage multiple databases and does not require all databases that contain datasets to be on the same Hard drive or even the same server to run.
   1. Consider a hard drive for your production and then a second storage area or hard drive for your historical datasets. 
      You should consider how fast is fast enough when accessing historical data.  
      See MSSQL Server sizing guidelines for Hard drive suggestions that may help your configuration decisions. 
2. When Greenstone assist your team to move from PSQL to MSSQL, AGRIS is configured for an instance called "Mixed Mode" to port data from PSQL to MSSQL. 
3. During that "Mixed mode" time many will find that overall both can run and are available from MSSQL and PSQL.   
4. Greenstone does not recommend "mixed mode" for continued operation 
5. A better approach may be
   1. Separate the PSSQL from the MSSQL environment to take advantage of all functionality within AGRIS. 
   2. Announce that there is a limited accessibility policy for historical data as the datasets are migrated to their new database. 
   3. Move data from the PSSQL environment configured as Mixed mode to the MSSQL environment as you have time taking advantage of the Export import feature to move MSSQL databases as required.
      MSSQL Dataset Export/Import
      
      
      

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:
  Error Message: Basic 2147217865 Selecting specific dataset(s)
• Page:
  MSSQL How To find the active connections to the database. (system or users)
• Page:
  MSSQL Transaction Timeout and Rollback