Changing the parallelism option to use only one processor will eliminate parallelism as an option for the query optimizer in its costing algorithm. This will also prohibit SQL Server from executing a single query across multiple processors. Unless the system is experiencing unbounded searches (user-executed or other), the selective nature of OnBase queries should prevent long execution times. Generally, a query should take no longer than 1 second to complete when given optimal factors and appropriately unique input criteria. With the expected index usage and optimal maintenance procedures in place (for example, up-to-date statistics, etc.), the server should not experience long-running queries.
If you prohibit all processors from being dedicated to a single query, queries that are errant (either because of poor query plans or because of inexperienced users) may not impact other users as significantly. If a single query is permitted to execute across all processors, access to the system can be severely limited for the remaining users.
Because queries generated by OnBase do not benefit from parallelism, and this setting has at times demonstrated errant behavior, parallelism should be disabled.
To disable parallelism in a server instance, navigate to the advanced properties of the server instance and set Max Degree of Parallelism to 1.
In SQL Server 2016 and later, the maximum degree of parallelism can be configured for individual databases, rather than the SQL Server instance. To disable parallelism for a specific database in SQL Server 2016 and later, navigate to the properties of the database and set Max DOP to 1.