[ https://issues.apache.org/jira/browse/JUDDI-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17156157#comment-17156157 ]
Alex O'Ree commented on JUDDI-1011: ----------------------------------- updating hibernate + using the ddl generator for newer versions of mssql, it does in fact use varchar(max) now. I found a few other fields that may have similar issues. This caused a few other unexpected issues with running queries on those fields. see the linked Jira for more information. > MS SQL Server table - length of field too large > ----------------------------------------------- > > Key: JUDDI-1011 > URL: https://issues.apache.org/jira/browse/JUDDI-1011 > Project: jUDDI > Issue Type: Bug > Components: core > Reporter: Steve Luisser > Priority: Major > > File mssql2000.ddl > > create table j3_tmodel_instance_info (id numeric(19,0) not null, > instance_parms varchar(8192), tmodel_key varchar(255) not null, entity_key > varchar(255) not null, primary key (id)); > > The instance_parms column exceeds the maximum length of a varchar field in > SQL Server of 8000 characters. I’ve reviewed the scripts for the other > database engines and the best option is to define this column as > instance_parms varchar(max). Another option is to define this column as > instance_parms varchar(8000) although if there was a good reason to make it > 8192 this value could overflow. -- This message was sent by Atlassian Jira (v8.3.4#803005)