fix bug with MSSQL and jiveSASLAuthoirzed_pk

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Incomplete
  • Affects Version/s: 3.1.1
  • Fix Version/s: 3.x
  • Component/s: Core
  • Labels:
    None
  • Environment:

    Windows: Microsoft SQL Server 7.00 - 7.00.1094 (Intel X86),
    Windows: SQL Server 2005

  • Acceptance Test - Add?:
    No

Description

I get an error when running the sqlserver script to set the databases up. The error is:
Server: Msg 1903, Level 16, State 2, Line 140
900 is the maximum allowable size of an index. The composite index specified is 4128 bytes.
Server: Msg 1750, Level 16, State 1, Line 140
Could not create constraint. See previous errors.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Cameron Moore added a comment -

I'm seeing the same behavior in 3.2.0 Beta.

A very complicated "work-around" can be found here: http://www.sqlmag.com/Article/ArticleID/93824/sql_server_93824.html

Another idea: would it be easier to simply create a hash of the username+principal and use the hash as a constraint?

Show
Cameron Moore added a comment - I'm seeing the same behavior in 3.2.0 Beta. A very complicated "work-around" can be found here: http://www.sqlmag.com/Article/ArticleID/93824/sql_server_93824.html Another idea: would it be easier to simply create a hash of the username+principal and use the hash as a constraint?
Hide
Permalink
Matt Tucker added a comment -

We should fix this if we can.

Show
Matt Tucker added a comment - We should fix this if we can.
Hide
Permalink
Daryl Herzmann added a comment -

any current reproducers?

Show
Daryl Herzmann added a comment - any current reproducers?
Hide
Permalink
Daryl Herzmann added a comment -

need updated information, then we can easily reopen, thanks.

Show
Daryl Herzmann added a comment - need updated information, then we can easily reopen, thanks.
Hide
Permalink
Lee added a comment -

This issue remains in 3.6.4 plus a new index now exists:

Warning! The maximum key length is 900 bytes.
The index 'ofRoster_jid_idx' has maximum length of 2048 bytes.
For some combination of large values, the insert/update operation will fail.

Warning! The maximum key length is 900 bytes.
The index 'ofSASLAuthorized_pk' has maximum length of 4128 bytes.
For some combination of large values, the insert/update operation will fail.

This definately makes the application unstable to use in SQL Server.

Show
Lee added a comment - This issue remains in 3.6.4 plus a new index now exists: Warning! The maximum key length is 900 bytes. The index 'ofRoster_jid_idx' has maximum length of 2048 bytes. For some combination of large values, the insert/update operation will fail. Warning! The maximum key length is 900 bytes. The index 'ofSASLAuthorized_pk' has maximum length of 4128 bytes. For some combination of large values, the insert/update operation will fail. This definately makes the application unstable to use in SQL Server.

People

  • Assignee:
    Gaston Dombiak
    Reporter:
    LG
Vote (2)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: