So we have created some scripts that will show us our possibly concurrency, but what does this mean and how do we work out how many session engines we will need. This article will explain, what a session engine is and why we need at least one of them. We will show you some test results that we have run with the Data Collection Load tool and some standard scripts.
In the previous articles we designed some scripts to read the IVW log files to work out what the concurrency was, next we will write a script that will try and Estimate what sort of concurrency certain survey criteria might produce. In this article we will take all the information that we have gathered from Data Collection Users to try and produce some example loads.
In the last two articles we took our log files and converted them into an MDD and a DDF file that we can use for reporting. In this article we will create a tables script and produce 3 tables that we will then export to excel.
In this article we are going to create the final DMS script that we use to recode the concurrents.csv file created in the previous article into something that is richer and usable for tabulation. The final output file will be in a DataCollection Data file ( ddf ) format. This article assumes that you have some basic knowledge of DMS and VBA scripting.
Ever wanted to know what has been going on with your DataCollection Server Web concurrents? Interested in finding out if you are going over your limit of allowable concurrents frequently? If the answer to these questions is yes , then this set of articles is for you. In it we will show you how to look at the log files produced on your servers and calculate what has been going on and when. It should be noted that this article assumes that you have some knowledge of Data Management scripts as well as Tables scripts and VBA.