Custom SQL Server Triggers vs Dynamics 365 Business Central 2023 Wave 2 (v23) metadata changes

Dynamics 365 ERP - Development

Custom triggers in SQL Server are no longer supported in Dynamics 365 Business Central 2023 Wave 2.
Cloud rules must be respected, and direct access to backend SQL for inserts, updates, deletes, etc., is no longer allowed.
Triggers should be refactored into stored procedures and invoked when needed in on-premises environments.
The SQL error preventing custom triggers is due to schema changes introduced for performance optimization.
Microsoft's response to the issue was to update official documentation on optimizing SQL Server performance.
On-premises deployments using TableType ExternalSQL can also encounter the same trigger error.
External tables are not considered part of Dynamics 365 Business Central, leading to restrictions on triggers in these tables.
The author prefers consistent behavior and suggests adding documentation to make others aware of the limitations.

Registered users can view the full text for FREE!