Latest SQl Server setup script produces a DB which doesn't work

[Ian Mitchell]

See item http://sparxsystems.com/forums/smf/index.php/topic,36058.0.html
The use of nvarchar(max) as a data type seems to have some bad effects, at least in my setup.
Tried with SQL Server 214 and SQl Server 2016 - they both show the same issue with the nvarchar(max) data type

[Eve]

I spoke with our DB experts.

At first they couldn't reproduce the problem. Eventually they discovered that the difference is that it works when using an OLE drive, but it doesn't when using an ODBC driver. Apparently although Microsoft has been recommending changing to use nvarchar(max) for 10+ years, their odbc driver still doesn't support it.

Note that our help does specify to connect using the OLE db provider. Not the ODBC driver.

http://www.sparxsystems.com/enterprise_architect_user_guide/13.0/model_repository/connecttosqlserver.html

[Geert Bellekens]

Good to know.

Is there an upgrade-script available to go from the ntext variant to the varchar(max) variant?
I think i'd like to have all my customers on the varchar(max) variant.
There are a number of sql server functions that don't work with ntext, but do with varchar (union, replace, ...)

(and we do follow instructions and use the OLE DB connector )

Geert