I know it is not allowed to be able to use SQL Triggers on the Sage 200 databases but I believe this should be considered
Andrew Siddles
| Idea Benefit | We are heavily involved with a middleware product which we have started to be able to create various projects that link into the Sage 200 Database but one of the ideas we have would need the use of SQL Triggers which would allow notifications within this program and allow the further enhancement of this new area |
| How do you solve for this problem today? | At the moment there isn't a work around to this |
| Product Variant | Sage 200 Professional |
SQL Triggers are not in line with our product terms, there are a wide variety of changes that could be done and some can alter the data to a structure that the business rules/logic doesn't support and ultimately could break/ damage the data or place the site in an unsupported state. You should be using the SDK or the API to make necessary changes.
On this basis this is not something we will consider for implementation.
As the previous comment outlines, there is some functionality in SQL to capture tracking as well.
Firstly you need to identify what your requirement actually is so that an idea can be formed as to whether it is possible or not with or without triggers. Secondly there is change tracking functions in SQL Server that don't use triggers: https://learn.microsoft.com/en-us/sql/relational-databases/track-changes/track-data-changes-sql-server?view=sql-server-ver16