Issues with changing from NTEXT to NVARCHAR(MAX)?

[Dan DeZurik]

I'd like to set up some indexes that contain some fields in the INCLUDE portion of the index. Being that the fields are NTEXT, they cannot be used. It's an easy change to alter the fields, but I'm wondering if anyone has done this before and ran into any issues?

The particular table I'm looking at is changeitem. We have a lot of queries that reference this table and setting up a better index would reduce the processing time and number of reads.
Here is the index I'm thinking of setting up provided I change OLDVALUE, OLDSTRING, NEWVALUE and NEWSTRING from ntext to nvarchar(max)

CREATE INDEX idx_chgitem_group_field_v2 ON dbo.changeitem (groupid, FIELD)
INCLUDE (FIELDTYPE, OLDVALUE, OLDSTRING, NEWVALUE, NEWSTRING)

[Josh Steckler]

@Dan DeZurik Did you ever end up doing this? Curious what you may have found.

[Dan DeZurik]

@Josh Steckler  We did not. Instead, the company decided to move away from Jira as there were too many issues.