I first suposed that if I create parameters for stored procedures and set parameter type as ftString I will see (in dbMonitor) String and for ftWideString I will see WideString.
Wrong. For MySQL I see that UseUnicode sets all string parameters to String or WideString accordingly.
With MySql if I change UseUnicode (connection param) to True or False in dbMonitor all string parameters "Data Type" is WideString or String.
With SQL Server regardless of UseUnicode, dbMonitor always show "Data Type" as String. And I can not use NVARCHAR in stored procedure. Nothing change if I set parameter to ftWideString.
I create parameters in this way:
Code: Select all
sqlspUSP_ValidareCodIntern.Params.CreateParam(ftWideString, FSQL_PrefixParam + 'MesajRaspuns', ptOutput).Size := 200;