Interface MsSqlDialectOptions

The tedious library to use. If not provided, the tedious npm library will be used. Must be compatible with the tedious npm library API.

Using this option should only be considered as a last resort, as the Sequelize team cannot guarantee its compatibility.

Whether string values are escaped & bound as Unicode (NVARCHAR) or as non-Unicode (VARCHAR) values.

When enabled (the default), string literals are prefixed with N and bound parameters use the NVarChar type, which matches the NVARCHAR columns Sequelize creates by default.

When disabled, string literals are emitted without the N prefix and bound parameters use the VarChar type. This is useful for schemas that use non-Unicode VARCHAR columns: comparing a VARCHAR column to a Unicode value forces SQL Server to implicitly convert the column for every row, which prevents the query optimizer from using an index seek on that column.