I choose "Data Audit" and then select a table, uncheck "Audit All Columns" but then the pop-up does not show any columns??

-- Solidguy

Thu Jun 22, 2006 2:10 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6509

Re: SQL Server 2005 -- columns not visible

1. Please ensure you have permissions to read column characteristics from the database system catalog. To verify that logon to SQL Server using SQL Query Analyzer or SQL 2005 Studio, select the correct database and run SELECT * FROM syscolumns. 2. The table contains at least 1 column having supported data types. For example, that table doesn't consist of a single LONG or IMAGE column.

: I choose "Data Audit" and then select a table, uncheck "Audit : All Columns" but then the pop-up does not show any columns??

: -- : Solidguy

Thu Jun 22, 2006 2:32 pm

Solidguy

Joined: 22 Jun 2006Posts: 4

Re: SQL Server 2005 -- columns not visible

Yes, the query works. I can also use Management Studio to browse the db and view all the columsn and column types But DB Audit 3.0 still comes up blank. I am trying to audit the "Adventure Works" database. The only columns I can see are those of tables owned by dbo. I am using "SQL Native Client" ODBC source.

: 1. Please ensure you have permissions to read column characteristics from the : database system catalog. To verify that logon to SQL Server using SQL : Query Analyzer or SQL 2005 Studio, select the correct database and run : SELECT * FROM syscolumns. : 2. The table contains at least 1 column having supported data types. For : example, that table doesn't consist of a single LONG or IMAGE column.

Thu Jun 22, 2006 3:05 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6509

Re: SQL Server 2005 -- columns not visible

Please take a look if you got db_audit.err file in the DB Audit directory and if yes, what you got at the end of the file.

: Yes, the query works. I can also use Management Studio to browse the db and : view all the columsn and column types : But DB Audit 3.0 still comes up blank. : I am trying to audit the "Adventure Works" database. : The only columns I can see are those of tables owned by dbo. : I am using "SQL Native Client" ODBC source.

SQLerrText: But this got created only when I clicked on "Enable System Audit" Needless to say "system audit" functionality does not work either.

: Please take a look if you got db_audit.err file in the DB Audit directory and : if yes, what you got at the end of the file.

Thu Jun 22, 2006 5:04 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6509

Re: SQL Server 2005 -- columns not visible

This error indicates some other issue. Somehow you lost xp_dbaudit.dll or run an old version. What I don't see there are database errors related to the column selection for the auditing.

You mentioned that can see columns in tables from dbo schema, but cannot see them in columns from other schemas. Are you connected as SA. Can you see these other columns when you connect as a user who owns the schema?

: SQLerrText: But this got created only when I clicked on "Enable System : Audit" : Needless to say "system audit" functionality does not work either.

Thu Jun 22, 2006 6:19 pm

Solidguy

Joined: 22 Jun 2006Posts: 4

Re: SQL Server 2005 -- columns not visible

I've tried a couple of things: 1. Connect as a user with all privileges (not SA). This user is authenticated via SQL Server 2. Connect as the owner of the db. This user is authenticated via Windows 3. Connect as sa. This actually makes the problem worse -- AdventureWorks is not even visible.

Both : This error indicates some other issue. Somehow you lost xp_dbaudit.dll or run : an old version. : What I don't see there are database errors related to the column selection : for the auditing.

: You mentioned that can see columns in tables from dbo schema, but cannot see : them in columns from other schemas. Are you connected as SA. Can you see : these other columns when you connect as a user who owns the schema?

Fri Jun 23, 2006 1:38 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6509

Re: SQL Server 2005 -- columns not visible

We actually received a copy of that db from you and we are planning to install and test this stuff today. I will get back to you as soon as I have any news.

: I've tried a couple of things: 1. Connect as a user with all privileges (not : SA). This user is authenticated via SQL Server : 2. Connect as the owner of the db. This user is authenticated via Windows : 3. Connect as sa. This actually makes the problem worse -- AdventureWorks is : not even visible.