Win32::SqlServer will only pass the data as varchar, if the ANSI code page of the client agrees with the code page of the database collation. This applies also if you are using an older provider than MSOLEDBSQL. Because of the changes in MSOLEDBSQL 18.4, I have removed this rule, and in 2.013 string data for sql_variant is always passed as nvarchar when the database code page does not agree with the ANSI code page of the client. In 2.012, Win32::SqlServer always sent string data for sql_variant as varchar when the database had an UTF-8 collation, no matter the client code page.There are some breaking changes with string data and the sql_varaint data type, due to changes that Microsoft introduced in version 18.4 of the MSOLEDBSQL provider. These restrictions are due to the limitations in the OLE DB providers. You need to use at least version 18.5 of the provider MSOLEDBSQL.You must be connecting to SQL 2019 or later.Win32::SqlServer now workts when you have set your ANSI and OEM code pages in Windows 10 to UTF-8 with these restructions:.The module have been tested with MSOLEDBSQL 18.6, which was the most recent version of this provider at the time of release of 2.013.The module itself continues to accept all Perl versions from 5.12 and up, though. Thus, I no longer supply binaries for Perl 5.20 and 5.22, nor have I tested with these versions.I have not tested with Strawberry Perl 5.34, as it was not avilable when I completed my release. All binaries up version 5.32 have been tested with Strawberry Perl. The property GeneralTimeout was always ignored together with one more, exactly which dependend on which OLE DB provider you were using. It seems that 2.013 introduced a bug by which some login properties were ignored.This is intended to mitigatge the change for encryption in MSOLEDBSQL19. New module-level routine SetDefaultForEncryption() which permits you to set the default for the login properties Encrypt, TrustServerCertificate and HostNameInCertificate directly after use.New login property HostNameInCertificate, which requires the new provider MSOLEDBSQL19.Beware that MSSQLOLEDB19 defaults to requiring that the connection to SQL Server is encrypted by a trusted certificate.I have tested Win32::SqlServer 2.014 against SQL 2022, CTP 2.0, which was the current pre-release version of SQL 2022 at the time of the release of 2.014.This version of Win32:SqlServer was released very shortly after the release of Perl 5.36, and no binary distribution was available at the time. For 5.34, only the 64-bit binary have been tested, since there is no free binary distribution of 32-bit Perl for that version. All versions up to Perl 5.32 have been tested with Strawberry Perl and/or ActivePerl. Support added for the new OLE DB provider MSOLEDBSQL19, which incurs some breaking changes, see below.Check the LD_LIBRARY_PATH variable and unset any references to Perl & Lib if these are set.History Win32::SqlServer History Win32::SqlServer – 2.014.Operating System: Linux distribution using glibc 2.15 or later (e.g.Administrative Privileges: On Windows 2003/Vista systems ActivePerl installations must be performed by a privileged user only. You may get an error message to this effect, or it may fail mysteriously. If you do, the Windows Installer Service will not be able to access the MSI file in order to perform the installation. System Account: (MSI Installer only) Do not launch the installation package from a directory for which the “System” account does not have read permission. Otherwise, these variables may cause incompatible versions of Perl modules to be used during the installation process.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |