Below are instructions for filling out the Spreadsheet for converting your custom tables/views/objects to Postgres: Instructions are provided for each spreadsheet in the folder for your program. Some don't need any action and some do require actions. 


A few notes:

  • You do not need to delete any tables/views that you do not intend to migrate. Just put a "N" in the column.
  • Please make sure that there are no blanks in the "Migrate" columns for those sheets that need action. There should either be a Y or N for every row.
  • We will send you another set of spreadsheets prior to your conversion that will capture any changes that you have made since this export. You should be able to copy/paste most of your values except for any new rows that are added.
  • If you have a NatureServe SharePoint account, you should be able to log in and go to this folder, find your program within that folder and then edit the CSV's directly in SharePoint. Extensible Tables and Views Exports 
  • If you do not have access to NatureServe SharePoint, you can easily request access. If you are on the Biotics POC list (which you all are) you should have gotten an invitation to join our tenant as a Guest. If you didn't do that or you never received access, please fill out this form and we will send another link for you to create an account. This will be useful going forward as we will need to do this again closer to conversion. Once you have access, you should be able to access the folder via this link: Extensible Tables and Views Exports and find your program and edit the spreadsheets directly in SharePoint.
  • If your organization does not allow access to Microsoft Office 365 or you don't believe you will be able to have a guest account, you can download the spreadsheets, open them as an Excel File, edit them, re-save them as a CSV, and then upload them and overwrite the existing file in SharePoint. It is important that these are named the same as the files that are currently in there or the conversion will not work properly. It may not be as big of an issue during this initial run, but it will be for the final production push, so it's best to make sure things are working properly now. 


Spreadsheets


  • Custom Date Columns:  This is a list of your custom date columns in your Biotics 5 database that will be converted. This is for your information only. No action is needed.
  • Custom Foreign Keys: This is a list of your extensible tables and their relationships to other tables. This is for your information only. No action is needed.
  • Custom Functions: This is a list of custom functions in your database. Action Needed: Please indicate in the Migrate column a "Y" for migrate or "N" do not migrate. Please make sure every row has either Y or N. 
  • Custom Numeric Columns: Certain numeric datatypes are changing during the migration process. This spreadsheet provides you with insight if there could be errors in your database that could cause issues during migration. Please look at the "Decimal Values Found" column for any rows with "Y" and investigate further and update any records that need to be updated. Although no action is required in this spreadsheet, you should make any updates to the data prior to conversion.
  • Custom Procedures: This is a list of custom procedures in your database. Action Needed: Please indicate in the Migrate column a "Y" for migrate or "N" do not migrate. Please make sure every row has either Y or N. 
  • Custom Tables: This is a list of custom tables in your database. Action Needed: Please indicate in the Migrate column a "Y" for migrate or "N" do not migrate. Please make sure every row has either Y or N. The other columns in this sheet are for your information. The only column needing action is the "Migrate" column.
  • Custom Views: This is a list of all of the custom views in your database. Action Needed: The first thing you should do is take a look and see if there are views in here you do not plan to migrate and mark those with "N". Then look at the remaining views. If there are views with Valid = "N" then you will need to look at that view and determine why it is not valid and fix it prior to migration. If it fails, it will not be migrated. If you are not migrating it, no need to fix it. Similarly, if the "Contains Problematic Outer Join" column contains a "Y", then you need to fix that outer join prior to conversion. There are Help Desk Solutions that can help fix these. After conversion there may need further refinement needed to get them to properly work in PostGres but they need to be valid in Oracle prior to conversion.