I'm getting the following error when I select a table and click proceed
to create the audit triggers via DB Audit.

"A database error occurred while your request was being processed. Here are the
details: 256 is the maximum allowable size of an index. Composite index
specified is 286 bytes."

The DB is Sybase 11.0.3 running on a WindowsNT box. Is there a setting I need to
change in Sybase to avoid this error?

This is probably caused by definition of the table primary key. Your version of Sybase has a limit of total 256 bytes for all columns included into index. DB Audit creates an audit trail table that mimics the original table and has several additional columns that also added to the index. This may cause the index to exceed 256 bytes.

Please post your table definition and existing primary key definition (if any) so I can provide you with a workaround.

: I'm getting the following error when I select a table and click proceed
: to create the audit triggers via DB Audit.

: "A database error occurred while your request was being processed. Here
: are the
: details: 256 is the maximum allowable size of an index. Composite index
: specified is 286 bytes."

: The DB is Sybase 11.0.3 running on a WindowsNT box. Is there a setting I need
: to
: change in Sybase to avoid this error?

***Columns***
Name Datatype Null Default Default Binding Rule Binding
Constituent_ID numeric(10,0) No dbo.Positive_Validation_Rule
Constituent_Name varchar(50) Yes
Recognition_Report_Name varchar(50) Yes
Constituent_Type char(1) Yes dbo.Const_Type_Rule
E_Mail_Address varchar(64) Yes
Webpage_Address varchar(255) Yes
Constituent_Number varchar(10) Yes
Active_SEVIS_Rcd char(1) No dbo.Set_to_N dbo.Yes_No_Rule

***Primary key***
Constituent_ID

***Logical primary key***
Constituent_ID

***Constraints***
Name Type Constraint
XPKConstituent PRIMARY KEY Constituent_ID

***Index dependencies***
1.) CREATE NONCLUSTERED INDEX XIE1Constituent

ON dbo.Constituent(Constituent_Name)

go
2.) CREATE CLUSTERED INDEX XIE2Constituent

ON dbo.Constituent(Constituent_Type,Constituent_Name)

go
3.) CREATE NONCLUSTERED INDEX XIE3Constituent

ON dbo.Constituent(Constituent_Number)

go
4.) CREATE NONCLUSTERED INDEX XIF1000Constituent

ON dbo.Constituent(Constituent_Type)

go

***TABLE DDL***
CREATE TABLE dbo.Constituent
(

Constituent_ID numeric(10,0) NOT NULL,

Constituent_Name varchar(50) NULL,

Recognition_Report_Name varchar(50) NULL,

Constituent_Type char(1) NULL,

E_Mail_Address varchar(64) NULL,

Webpage_Address varchar(255) NULL,

Constituent_Number varchar(10) NULL,

Active_SEVIS_Rcd char(1) NOT NULL,

CONSTRAINT XPKConstituent

PRIMARY KEY NONCLUSTERED (Constituent_ID)
)
go
EXEC sp_primarykey 'dbo.Constituent', Constituent_ID
go
EXEC sp_bindrule 'dbo.Positive_Validation_Rule','Constituent.Constituent_ID'
go
EXEC sp_bindrule 'dbo.Const_Type_Rule','Constituent.Constituent_Type'
go
EXEC sp_bindefault 'dbo.Set_to_N','Constituent.Active_SEVIS_Rcd'
go
EXEC sp_bindrule 'dbo.Yes_No_Rule','Constituent.Active_SEVIS_Rcd'
go

I can also provide trigger and procedure dependencies if you need that informaion too.

Regards,
Mth_42

: This is probably caused by definition of the table primary key. Your version
: of Sybase has a limit of total 256 bytes for all columns included into
: index. DB Audit creates an audit trail table that mimics the original
: table and has several additional columns that also added to the index.
: This may cause the index to exceed 256 bytes.

: Please post your table definition and existing primary key definition (if
: any) so I can provide you with a workaround.

I don't see why this is causing any problems, there is only one numeric column in the key. I am forwarding this case to support for detailed analisys.

: ***Columns***
: Name Datatype Null Default Default Binding Rule Binding
: Constituent_ID numeric(10,0) No dbo.Positive_Validation_Rule
: Constituent_Name varchar(50) Yes
: Recognition_Report_Name varchar(50) Yes
: Constituent_Type char(1) Yes dbo.Const_Type_Rule
: E_Mail_Address varchar(64) Yes
: Webpage_Address varchar(255) Yes
: Constituent_Number varchar(10) Yes
: Active_SEVIS_Rcd char(1) No dbo.Set_to_N dbo.Yes_No_Rule

: ***Primary key***
: Constituent_ID

: ***Logical primary key***
: Constituent_ID

: ***Constraints***
: Name Type Constraint
: XPKConstituent PRIMARY KEY Constituent_ID

: ***Index dependencies***
: 1.) CREATE NONCLUSTERED INDEX XIE1Constituent

: ON dbo.Constituent(Constituent_Name)

: go
: 2.) CREATE CLUSTERED INDEX XIE2Constituent

: ON dbo.Constituent(Constituent_Type,Constituent_Name)

: go
: 3.) CREATE NONCLUSTERED INDEX XIE3Constituent

: ON dbo.Constituent(Constituent_Number)

: go
: 4.) CREATE NONCLUSTERED INDEX XIF1000Constituent

: ON dbo.Constituent(Constituent_Type)

: go

: ***TABLE DDL***
: CREATE TABLE dbo.Constituent
: (

: Constituent_ID numeric(10,0) NOT NULL,

: Constituent_Name varchar(50) NULL,

: Recognition_Report_Name varchar(50) NULL,

: Constituent_Type char(1) NULL,

: E_Mail_Address varchar(64) NULL,

: Webpage_Address varchar(255) NULL,

: Constituent_Number varchar(10) NULL,

: Active_SEVIS_Rcd char(1) NOT NULL,

: CONSTRAINT XPKConstituent

: PRIMARY KEY NONCLUSTERED (Constituent_ID)
: )
: go
: EXEC sp_primarykey 'dbo.Constituent', Constituent_ID
: go
: EXEC sp_bindrule 'dbo.Positive_Validation_Rule','Constituent.Constituent_ID'
: go
: EXEC sp_bindrule 'dbo.Const_Type_Rule','Constituent.Constituent_Type'
: go
: EXEC sp_bindefault 'dbo.Set_to_N','Constituent.Active_SEVIS_Rcd'
: go
: EXEC sp_bindrule 'dbo.Yes_No_Rule','Constituent.Active_SEVIS_Rcd'
: go

: I can also provide trigger and procedure dependencies if you need that
: informaion too.

: Regards,
: Mth_42

It appears that DB Audit by default does not create any indexes on audit trail tables and there should not be any problems with indexes. The error message is probably incorrect and is a side-effect of some other issue. Please enable tracing and run the Generate Triggers operation again. Please see "Troubleshooting the database connection" "topic in the on-line help for instructions on how to enable "database trace". After enabling the trace please reproduce the error and then email the generated trace file to support@softtreetech.com.

: I don't see why this is causing any problems, there is only one numeric
: column in the key. I am forwarding this case to support for detailed
: analisys.

Here is what we found out.

DB Audit creates two catalog tables to store information about tables and columns being audited. Both tables have primary keys containing several VARCHAR(128) columns. Sybase 11.0 has a limitation of maximum 256 bytes in all columns in an index. This limitation causes the catalog creation process to fail because the primary keys cannot be created. To resolve this issue we developed new DB Audit patch 2.0.20 which for Sybase version 11.0 and prior defines primary key columns as VARCHAR(64) rather than as VARCHAR(128) as for all other database systems and later Sybase versions (12.0+).

This patch can be download using the main download link available on the product home page http://www.softtreetech.com/dbaudit.

: It appears that DB Audit by default does not create any indexes on audit
: trail tables and there should not be any problems with indexes. The error
: message is probably incorrect and is a side-effect of some other issue.
: Please enable tracing and run the Generate Triggers operation again.
: Please see "Troubleshooting the database connection" "topic
: in the on-line help for instructions on how to enable "database
: trace". After enabling the trace please reproduce the error and then
: email the generated trace file to support@softtreetech.com.