If you require a Microsoft SQL Server license based on the number of concurrent connections, the table below can assist you in estimating the required connection limit.
Note that the overview offers an estimate only. Make sure that your Microsoft SQL Server offers sufficient concurrent connections. More surveys and more NIPO FMS client connections require more concurrent Microsoft SQL Server connections, while more interviewers and web respondents do not.
| System / action
|
Connections
|
NIPO CATI / Web Master
|
|
ContactLog table
|
2
|
Interviewer table
|
1
|
InterviewerLog table
|
1
|
Survey table
|
1-2
|
StationKeys table (used only with remote NIPO CATI Clients)
|
1
|
Each running survey using a Sample table
|
2-3
|
*SQLPUT, *SQLGET, *SQLADD, *NEXTRECORD commands in the NIPO ODIN questionnaire
|
1 for each running survey
|
Dialer
|
0
|
NIPO FMS Server
|
|
NIPO FMS Server service
|
2-6
|
Service threads
(checking for new surveys, sending mails, checking for reminders, et cetera)
|
1 per thread. Note that the frequency with which threads are executed can be configured in the NIPO FMS Client.
|
NIPO FMS Client
|
1-2 each. Note that connections are closed when exiting the application but may linger a number of minutes.
|
Sample table opened in a NIPO FMS Client
|
1 each
|
Search dialog opened in a NIPO FMS Client
|
1 each
|
NIPO Web Server (OdinServlet)
|
Maximum 5 (may be configured in the DatabasePoolLimit setting in the WEB.XML file). Note that NIPO Web Servers may be pooled, and that each will add its separate maximum.
|
Odin Demon
|
0
|
NIPO CATI / Web Manager
|
0
|
NIPO CATI Client
|
0
|
NIPO Web Client
|
0
|
Recovery tool (RECINT32.EXE)
|
0
|
NIPO Strand extracting data from a survey with a sample table
|
1
|
|
|
