| Issue Number | 4316 |
|---|---|
| Summary | Refresh CDR DEV Database |
| Created | 2017-09-21 15:20:01 |
| Issue Type | Improvement |
| Submitted By | Englisch, Volker (NIH/NCI) [C] |
| Assigned To | Englisch, Volker (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2018-06-22 14:29:15 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/ocecdr/issue.214614 |
Once the Fermi release completed we want to refresh the database on DEV.
~bkline, did we refresh
the CDR database on DEV as part of the SQL Server 2016 upgrade? I know
we did for QA and STAGE.
If DEV was refreshed as well we should be able to close this ticket.
No, we haven't refreshed DEV since January 2016. Here's how I go about finding out when the last refresh was:
bring up https://cdr-dev.cancer.gov/cgi-bin/cdr/CdrQueries.py
run the query {code:sql}
SELECT started, messages
FROM pub_proc
WHERE pub_subset LIKE 'Push_Documents_To_Cancer.Gov%'
ORDER BY id DESC
That's not a dumb idea! :-)
I've created the query DB Refresh from PROD on PROD because I tend to forget stuff.
~bkline, I'm thinking to
dive into a nice clean DB refresh very soon (Friday?).
Are we ready? (I know I am and many of our users/testers)
After some consideration we decided to wait with the DB refresh until after our Hawking release landed on PROD. This way the Hawking release will be part of DEV when the nightly database backup from PROD is being restored.
The CDR database on DEV has been refreshed on June 15th.
Closing ticket.
Elapsed: 0:00:00.001205