| > * use LISTEN to be notified of rows that have changed that the backend needs to take action on (so you're not actively polling for new work) > * use NOTIFY from a trigger so all you need to do is INSERT/UPDATE a table to send an event to listeners Could you explain how that is better than just setting up Event Notifications inside a trigger in SQL Server? Or for that matter just using the Event Notifications system as a queue. https://learn.microsoft.com/en-us/sql/relational-databases/s... > * you can select using SKIP LOCKED (as the article points out) SQL Server can do that as well, using the READPAST table hint. https://learn.microsoft.com/en-us/sql/t-sql/queries/hints-tr... > * you can use partial indexes to efficiently select rows in a particular state SQL Server has filtered indexes, are those not the same? https://learn.microsoft.com/en-us/sql/relational-databases/i... |