Like Advanced Reporting and Skype for Business monitoring, Dynamic Threshold has its own DTfax which contains a lot of system configuration information, collector logs and troubleshooting data. Prognosis has shiiped with the Dtfax script to run and collect the information. To generate the DTFax, there are two scenarios.
When the SQL Server and Prognosis Dynamic Threshold solution are deployed on the same server, the way to run it is very simple, just navigate to the <Prognosis>\Server\Configuration\DynamicThreshold\<deploymentName> folder, and double click on the Windows batch file Dtfax.bat, it will run and generate the DTfax.csv file in the same location.
Note, the deploymentName is the given name when you deploy Dynamic Threshold solution.
Scenario 2
When the SQL Server is a dedicated server, i.e., Prognosis Dynamic Threshold solution are deployed on one server and the SQL Server on another server, then the DTfax generating process is different.
In this case, the script needs to know the SQL server instance name, login credentials and such to be able to connect to the SQL server.
First, navigate to the dtfax folder, then edit the run.bat file:
The run.bat file has below syntax:
sqlcmd -S <hostname>\<instance> -U SA -P <password> -d DTPredictions -W -s, -i allScripts.sql -o dtfax.csv
For example, a real command line would look like:
sqlcmd -S mySQLServerName\DTInstanceName -U userID -P myPassword -d DTPredictions -W -s, -i allScripts.sql -o dtfax.csv
You can run this command from command window (run as Administrator), or simply run the run.bat file.
The dtfax.csv file will be generated in the same location.
