MonitorWare Knowledge Base

Are there any known problems with setting winsyslog to log to a ms sql server with a primary key or indexes setup. I ask because when I had initially set the database and then added a primary key on the UID and and index on the date and ip, I started getting lots of input errors in the app log of the server. like

Code: Select all

Event Type:   Error
Event Source:   AdisconWinSyslog
Event ID:   114

Computer:   SQLSERVER
Description:
Error while applying an action - skipping this action. Error is 'ODBC Error Code: '37000'
ODBC Error Description: '[Microsoft][ODBC SQL Server Driver][SQL Server]INSERT failed because the following SET options have incorrect settings: 'ARITHABORT'.'.'.

I would set arithabort on for the entire database and then get

Code: Select all

Event Type:   Error
Event Source:   AdisconWinSyslog
Event ID:   114

Computer:   SQLSERVER
Description:
Error while applying an action - skipping this action. Error is 'ODBC Error Code: '37000'
ODBC Error Description: '[Microsoft][ODBC SQL Server Driver][SQL Server]Only text pointers are allowed in work tables, never text, ntext, or image columns. The query processor produced a query plan that required a text, ntext, or image column in a work table.'.'.

If anything, is there a recommended setup for indexing and a primary key?
I ended up just creating the default DB from the help file, but it is starting to get big and performance is lagging

much appreciated

Hi,

there is a MS Access sample database installed with WinSyslog.
Import this database into MSSQL, then you will have a working table with a Primary Key which auto increments.