BSP Views

Several views have been created to access data directly from the BSP database. These views can be quite computationally heavy, in which case they can feed a table through periodic ETL. The informatics team is always making updates to the BSP database, and we want to ensure that the views don't break as a result of DB changes.

We've created a table that will tell the informatics team if any of their changes break our views.  To add a new view to their tests, follow this procedure:

1. In SQL Navigator (or similar tool), log in to analytics at GAP_PROD.
2. Ensure that the "Updateable" button is turned on.
   1.   
3. Run the command: SELECT * FROM BSP_ANALYTICS_VALIDATION table.
4. Add a new row to the table.
   1. ID should be the next unused integer.
   2. INVOCATION: select * from analytics.<new view name> where rownum<10
      1. rownum<10 is a way to increase chances of hitting different data types during the invocation (instead of choosing just row 1)
   3. ENABLED: 1
      1. you can add a row and place a zero in ENABLED to avoid running the invocation, using the row as a temporary placeholder
   4. COMMENTS can be notes about placeholder, purpose of view, etc.
   5. KIND should generally be "query"
5. Once the new row is added, click the COMMIT button.
   1.