Today my good friend Aaron Lowe (Blog | Twitter) let me know he was having problems getting SQLCop to run. The error would come up as soon as the executable would be run to do the initial install and run of the program. Proxy servers lock down internet traffic to the point explicit allowances must be set in order for programs like SQLCop to function.
SQLCop uses an internet connection to ensure that all checks and updates that are added are maintained. When SQLCop first loads, it checks the SQLCopConfig.xml file to determine if a new SQLCop.xml file needs to be downloaded. If SQLCop is unable to download the configuration file, it will automatically use the previously saved sqlcop.xml file. Because of this, a remote file request is always performed when you start up SQLCop.
In order to work around this problem with proxy servers there is one of two things you can do to run SQLCop.
- Ask the network administrator to add the changes to the proxy
- Download two XML files from LessThanDot that are required by SQLCop
The two files are very lightweight! So don’t be scared. They really won’t bite.
The first is the SQLCop.xml. This file holds all of the checks and links to resources that SQLCop uses.
The second file is the SQLCopConfig.xml. This file holds the version levels of SQLCop which is important to know where the version and update levels SQLCop are at.
Place these two files in the same directory as the SQLCop.exe and SQLCop will run without requiring the check for any updates or pull down new updates to these files.
We appreciate everyone’s feedback on SQLCop and any problems or suggestions that you have are always welcome. You can post forum topics on LessThanDot to let us know. Also, SQLCop and LessThanDot is run and maintained from donations. If you can help, we greatly appreciate it. 🙂