On Mon, Dec 13, 2010 at 02:23:18PM -0500, Shawn Cannon wrote:
OK this is some good info. It looks like even though I specify the database name, it is someone how using it and tries to create or check for the tables on the master database. Any ideas? Here is the info from the capture. Why is is running a SELECT looking for syslogng instead of the database name?
For this we will probably need help from the syslog-ng team proper. It could take a couple of days since they are in Europe / CET Zone. Meanwhile, please read over this chapter from the manual to see if you can work around the problem somehow: http://www.balabit.com/sites/default/files/documents/syslog-ng-ose-v3.2-guid... 3.6. Configuring Microsoft SQL Server to accept logs from syslog-ng There have been some glitches in the support for DB configuration before. Such as port numbers being ignored and hard coded to defaults by mistake. This happens because libdbi is a third party library that's not part of the core code. Matthew.