Topic
When creating a SQL ServiceObject for a SQL database, sometimes the GUI "spins" and does not return. This is normally because there are "too many" SQL objects to discover, and the connection between the SQL backend and the UI fails/times out. (Your usage may vary, depending on SQL server resources, network connection issues, and other external factors.)
At the time of writing, K2 discovers all SQL objects. (Tables, Views and SPROCS) To workaround this, one can deny rights on the SQL objects that you are not going to be used, for the account that will register the ServiceObject. This way, the account cannot access the objects, and in doing so, does not need to discover/describe them.
Instructions
Please see the following Microsoft article on how to deny object permissions in SQL.
Additional Information
Please see the Considerations section in the documentation for more information.
Help documentation: https://help.nintex.com/en-US/k2cloud/userguide/current/default.htm#ServiceBrokers/SQLServer/SQL-Server-Service.htm
Documentation snippet...
- Depending on the size of the SQL database being referenced, registering or refreshing a Service Instance may take several minutes to complete.
- You may want to use SQL permissions to limit the access of the account used to discover the SQL entities, so that K2 only discovers the entities that the account has access to. This approach can also be used to restrict the number of entities K2 discovers and generates Service Objects for, when registering or refreshing the service.
