In the past, I have posted on the way the sysdba user needs to be configured in SQL Management Studio (here). Beginning with version 10.0, Infor CRM SLX requires a second user to be set up in SQL. In this case, the WebDLL windows user needs to granted login rights to SQL, and made a database owner for the SLX database.
As to why this is necessary, Infor CRM SLX 10.0 now includes the ability to use asynchronous session states in IIS. While this can be disabled by editing a few config files, you will want to have it working if possible. To oversimplify a bit, when the web client page makes a request of the web server without async, that request creates a session, and other requests must wait for that session to disconnect before creating their own session. This is true even if the two request could exist fine simultaneously. With asynchronous session state enabled, a request can drop its session while waiting for a response, thus preventing traffic jams. Depending on what sort of requests your web client is making, asynchronous sessions can give you a noticeable increase in speed.
In order for asynchronous sessions to work, you must add the WebDLL user to the SQL server instance that hosts the CRM database. Your SQL server needs to be in mixed-mode authentication, supporting both Window and SQL authentication. It likely already is, but you can check this in SQL Management Studio by right clicking the SQL Server instance, selecting Properties, and then selecting Security. If SQL Server and Windows Authentication Mode is not selected, change it to that.
Still in SQL Management Studio, you now need to add the WebDLL user (or whatever service account you are using for the application pool in IIS) as a Windows authentication user to that SQL instance. Expand the SQL Sever instance, expand Security, right click Longs and select New Login. With Windows Authentication selected, click Search, and search for the WebDLL user. Make sure to have it search the domain for the WebDLL user, rather than just the SQL server. (This will differ from the screenshot, as my test system is not in a domain.) Do not give it any Server Role beyond the default Public role. Now click User Mapping, select your Infor CRM SLX database, and grant WebDLL the db_owner for that database.
To complete the set up, expand the Infor CRM SLX database, the expand the Security under that database. Open the WebDLL user, select Owned Schemas, and add sysdba to the schemas owned by this user. It now has the rights it need for asynchronous session state to work.
