Initial Release - Version 0.90

Rating: No reviews yet
Downloads: 54
Change Set: 100831
Released: Dec 12, 2012
Updated: Dec 13, 2012 by ChadTillekeratne
Dev status: Alpha Help Icon


Application AzureDiagnosticsProcessorServiceSetup.msi
application, 173K, uploaded Dec 13, 2012 - 24 downloads
Source Code CreateAzureDiagnosticsDatabase.sql
source code, 43K, uploaded Dec 13, 2012 - 30 downloads

Release Notes

Initial release of WAD2SQL. This release is to provide basic functionality and may be expanded upon in the future (parallel async processing, pull service metadata, web logs, smoother installation, etc.).


  1. Create a new database on an existing SQL server
  2. Create Azure Diagnostics SQL database objects using the CreateAzureDiagnosticsDatabase.sql Script. Update the database name as needed.
  3. Insert the desired storage account name and key into the StorageAccount table.
  4. Run the AzureDiagnosticsProcessorServiceSetup.msi, then update the connection string (ApplicationDiagnosticsDatabase) in the C:\Program Files (x86)\wad2sql\crmbl.Azure.AzureDiagnosticsProcessor.exe.config .
  5. Restart the wad2sql service

Other/Advanced Configuration:

If you choose to utilize the more advanced functionality, run the Setup file prior to creating the database, then stop the service. This will allow you to update the service configuration prior to initial processing.

crmbl.Azure.AzureDiagnosticsProcessor.exe.config Values

  • ApplicationDiagnosticsDatabase - Connection String for the SQL database where diagnostics data will be stored.
  • FirstDataStartingDateOffset - During the initial processing of a service account, the application will use this value as a day offset. To pull everything in the storage account diagnostics tables, enter a large number (EG - 99999999).
  • ServiceLoopWaitIntervalMS - The time in which the process will wait before pulling more data (in MS). During initial loads, you may want to lower the time to allow for a faster catch up, then raise the time after catch up to minimize storage calls.
  • Logger-EventLog-LogName - Windows Event Logging Log Name, by default Application is used. If the application cannot write to the specified log, it will default to the Application Event Log
  • Logger-EventLog-Source - The Windows Event log entry source for application logging.

Reviews for this release

No reviews yet for this release.