[cvsnt] Re: B2141: MS SQLServer and audit trigger error

[someone aperson]

I created the database, and a user named cvsntHistory. I gave cvsntHistory
all rights to the database.
I then used the control panel to test the database access, and create the
tables.
I didn't manually create the tables using the Sql Scripts.

If 'count' isn't a field in one of the tables, then perhaps a sql script
syntax error is being generated.
I'll take a look at tracing the database on monday and see what is happening
on the sql side when i do a commit.

Joe E.

"Bo Berglund" <bo.berglund at telia.com> wrote in message
news:nronm19b0r70kg2no5sj58abj0s7qe04kl at 4ax.com...
> On Fri, 4 Nov 2005 16:56:20 -0500, "Joe Enfield"
> <joeenfield at hotmail.com> wrote:
>
> >on a test server with build 2141, I created a SQLServer database, and
turned
> >on auditing.
> >
> >after a commit:
> >------------------------
> >audit_trigger error (loginfo): [Microsoft][ODBC SQL Server Driver]COUNT
> >field incorrect or syntax error
> >
> >Success, CVS operation completed
> >-------------------------
> >
> >Looks like other information is getting to the data base tables.
> >SessionLog, and HistoryLog have quite a bit of info
> >Commit log has one entry, after two commits against three files.
> >
>
> I have absolutely no problems with an MSSql database, full audit
> switched on and using build 2141.
> And, there is *no* column named 'count' in any of the auditing tables.
> Did you create the tables using the mssql script shipped with the
> installer?
>
> In commitlog there should be one record for each file committed.
> In sessionlog there is one record for each cvs session, this is linked
> to the commitlog entries and carry the timestamp, user etc.
>
> I have also tested auditing with the SQLite backend, it also works
> very well. But since I am used to MSSql since years I switched back to
> that. Absolutely no probs.
>
>
> /Bo
> (Bo Berglund, developer in Sweden)