Cerenade Extractions: Pre-Extraction Database Optimizations

Cerenade Extractions: Pre-Extraction Database Optimizations

At one point in Cerenade's development history, it stored documents directly within its own database.
The Cerenade developers later migrated the documents to Azure storage, however, artifacts may still exist in customer databases who have been using Cerenade for a long time.
Because these artifacts can slow down the data extraction, we highly recommend purging them.  To do so, run the following scripts:


  2. UPDATE CaseInsuranceClaimDocuments SET FileContent = null WHERE FileStorageLocationID = 3
  3. UPDATE OrganizationDocuments SET FileContent = null WHERE FileStorageLocationID = 3
  4. UPDATE ClientVisas SET FileContent = null WHERE FileStorageLocationID = 3
  5. UPDATE CaseUSCISReceipts SET FileContent = null WHERE FileStorageLocationID = 3
  6. UPDATE QuestionnaireDocuments SET FileContent = null WHERE FileStorageLocationID = 3
  7. UPDATE ClientCustomDocuments SET FileContent = null WHERE FileStorageLocationID = 3
  8. UPDATE ClientDocuments SET FileContent = null WHERE FileStorageLocationID = 3
  9. UPDATE CaseCustomReceipts SET FileContent = null WHERE FileStorageLocationID = 3
  10. UPDATE ClientI94s SET FileContent = null WHERE FileStorageLocationID = 3
  11. UPDATE InternalEmailDocuments SET FileContent = null WHERE FileStorageLocationID = 3
  12. UPDATE CaseDocuments SET FileContent = null WHERE FileStorageLocationID = 3
  13. UPDATE ClientPassports SET FileContent = null WHERE FileStorageLocationID = 3
  14. UPDATE ClientPictures SET FileContent = null WHERE FileStorageLocationID = 3
  15. UPDATE CaseHealthcareLogDocuments SET FileContent = null WHERE FileStorageLocationID = 3