Error on creating of a new index

[Alexsey]

Expected behavior

New index should be created

Current behavior

Error occurs on attempt to create a new index

Failure information (for bugs)

If I create a new index from the UI and then press "Save" an error is occurs an no index is creating. Some error would be for "UNIQUE", "FULLTEXT" and "SPATIAL" types of indexes

Steps to reproduce

Please provide detailed steps for reproducing the issue.

Attempt to create "UNIQUE" index:

1. Open Table: tableName tab
2. Right click on a column name and select "Create a new index" -> "UNIQUE"
3. Click Save

Alert would popup with a text "SQL Error (1081): Incorrect syntax near 'INDEX'. If this is intended as a part of a table hint, A WITH keyword and parenthesis are now required. See SQL Server Books Online for proper syntax."

And here is a text from query log:

ALTER TABLE "dbo"."User"
	ADD UNIQUE INDEX "payerName" ("payerName");
/* SQL Error (1018): Incorrect syntax near 'INDEX'. If this is intended as a part of a table hint, A WITH keyword and parenthesis are now required. See SQL Server Books Online for proper syntax. */

On attempt to create "FULLTEXT" index errors would be:

Alert: "SQL Error (173): This definition for column 'FULLTEXT' must include a data type"

And query log:

ALTER TABLE "dbo"."User"
	ADD FULLTEXT INDEX "payerName" ("payerName");
/* SQL Error (173): The definition for column 'FULLTEXT' must include a data type. */

On attempt to create "SPATIAL" index errors would be:

The same as for "FULLTEXT" but with "SPATIAL" instead of "FULLTEXT" in error messages

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• HeidiSQL version: 9.4.0.5192
• Database system + version: Microsoft SQL Server 2016 (SP1-CU2) (KB4013106) - 13.0.4422.0 (X64)
  Express Edition (64-bit) on Windows Server 2012 R2 Standard 6.3 (Build 9600: ) (Hypervisor)
• Operating system: Windows 10

[ansgarbecker]

No problem

[Alexsey]

@ansgarbecker I have update the body. Can you, please reopen now?