# nvarchar(max) not supported on SQL Server

**URL:** <https://forum.liquibase.org/t/nvarchar-max-not-supported-on-sql-server/641>\
**Category:** General Discussion\
**Created:** [July 23, 2010, 2:32pm UTC](https://forum.liquibase.org/t/nvarchar-max-not-supported-on-sql-server/641 "2010-07-23T14:32:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pcleto](https://avatars.discourse-cdn.com/v4/letter/p/f19dbf/32.png) [@pcleto](https://forum.liquibase.org/u/pcleto)\
**Post date:** [July 23, 2010, 2:32pm UTC](https://forum.liquibase.org/t/nvarchar-max-not-supported-on-sql-server/641/1 "2010-07-23T14:32:00Z")

</div>

Hi  
I’ve been using this great tool for a while and just want to say that it has saved our team lots of times when trying to resolved schema upgrade problems.

I’m using a build of liquibase based on revision 1586 (RC3-SNAPSHOT) and I have an exception being thrown on a NVarchar column in a SQL Server 2005 defined as:

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 

the exception is

java.lang.NumberFormatException: For input string: "MAX" &nbsp; &nbsp; &nbsp; &nbsp; at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) &nbsp; &nbsp; &nbsp; &nbsp; at java.lang.Integer.parseInt(Integer.java:447) &nbsp; &nbsp; &nbsp; &nbsp; at java.lang.Integer.parseInt(Integer.java:497) &nbsp; &nbsp; &nbsp; &nbsp; at liquibase.database.typeconversion.core.AbstractTypeConverter.addPrecisionToType(AbstractTypeConverter.java:234) &nbsp; &nbsp; &nbsp; &nbsp; at liquibase.database.typeconversion.core.AbstractTypeConverter.getDataType(AbstractTypeConverter.java:226) &nbsp; &nbsp; &nbsp; &nbsp; at liquibase.database.typeconversion.core.MSSQLTypeConverter.getDataType(MSSQLTypeConverter.java:56) &nbsp; &nbsp; &nbsp; &nbsp; at liquibase.database.typeconversion.core.AbstractTypeConverter.getDataType(AbstractTypeConverter.java:162) &nbsp; &nbsp; &nbsp; &nbsp; at liquibase.database.typeconversion.core.MSSQLTypeConverter.getDataType(MSSQLTypeConverter.java:42) &nbsp; &nbsp; &nbsp; &nbsp; at liquibase.change.core.CreateTableChange.generateStatements(CreateTableChange.java:48)
Is there any known work-around for this column type?

Issue created: [http://liquibase.jira.com/browse/CORE-674](http://liquibase.jira.com/browse/CORE-674)  
TIA

---

<div class="post-metadata">

**Author:** ![nvoxland](https://avatars.discourse-cdn.com/v4/letter/n/87869e/32.png) [@nvoxland](https://forum.liquibase.org/u/nvoxland)\
**Post date:** [July 23, 2010, 2:32pm UTC](https://forum.liquibase.org/t/nvarchar-max-not-supported-on-sql-server/641/2 "2010-07-23T14:32:00Z")

</div>

It should be fixed in trunk now.&nbsp; THanks for creating the issue in jira.

Nathan

---

<div class="post-metadata">

**Author:** ![pcleto](https://avatars.discourse-cdn.com/v4/letter/p/f19dbf/32.png) [@pcleto](https://forum.liquibase.org/u/pcleto)\
**Post date:** [July 23, 2010, 2:32pm UTC](https://forum.liquibase.org/t/nvarchar-max-not-supported-on-sql-server/641/3 "2010-07-23T14:32:00Z")

</div>

Thanks a lot for the quick fix.