Sage CRM Upgrade SQL queries to run prior to starting

Sage CRM Upgrade SQL queries to run prior to starting

When upgrading Sage CRM you will be prompted to disable SQL triggers.  To disable SQL triggers run the following query which is found in KB #23931 

To disable all triggers: 
USE CRM 
GO 
EXEC sp_msforeachtable "ALTER TABLE ? DISABLE TRIGGER ALL" 
GO

drop index email.IDX_email_deleted 
drop index activity.IDX_Acty_LogoutMethod 
drop index activity.IDX_acty_SID 
drop index SyncResource.IDX_SYRS_uuid 
drop index locks.IDX_Lock_TableId_RecordId 
drop index Custom_ReportSearches.IDX_ReSe_ReportSearchName 
drop index ddata.IDX_DData_ShortStr 
drop index custom_tables.IDX_Bord_Caption 
drop index CoachingCaptions.IDX_Coch_ActionID 

If there are any CUSTOM triggers that the customer is using than should revise this script to list the specific triggers listed within the message when doing CRM upgrade to ensure that custom ones aren't being excluded from the upgrade.

Then to re-enable triggers:
USE CRM
GO
EXEC sp_msforeachtable "ALTER TABLE ? ENABLE TRIGGER ALL"
GO
    • Related Articles

    • CRM USER LOCKED OUT

      Login as Admin and go to the User. Find and press Unlock User button on the right hand side of the screen. OR Login to SQL Server Management studio - CRM database -User table - Edit Column USER_AccountLockedOut column to NULL.
    • Troubleshooting Sage CRM Dashboards failing to load

      Then this is due to tomcat having problem recognizing external host name (crm.ADSS.com) and still using just the internal server name ( ie ADSSSERVER)             Following this KB article will quickly resolve this issue :  Modify the host file :  ...
    • Sage CRM Mobile error when adding note

      Error related to CRM Mobile App when adding a Note or trying to Sync data back to the server. Download Error The current operation couldn't be completed. (NSURLErrorDomain error - 1012).  Cause: Certain CRM views were not properly installed for the ...
    • CRM freezes when updating Company record linked to Sage 300

      The issue was due to the "NET://" was not at the beginning of the location field within the Sage 300 Company Setup so once that was applied it fixed the issue with syncing from CRM to Sage 300.
    • "An error has occurred" via Sage CRM Mobile App

      1. For making the web URL visible on mobile devices<br/><br/> => Go to <CRM Insatllation drive>\CRM\tomcat\conf\ <br/> => Open server.xml<br/> => Add address="0.0.0.0" to Connector string e.g. <Connector port="8080" protocol="HTTP/1.1" ...