Installation Failed; Possibly Due to Collation?

Good afternoon.  I just tried to install SQL DM, but got "IDERA SQLdm Installation was unsuccessfull (sic)."  Looking in the log file at C:\Program Files\IDERA\SQLdm x64 Installation Kit\InstallSQLDM.log, I see just one thing which looks like it could be the cause:

1: ADO Error: Number: -2147217900 Description: The object 'ReverseMojibake' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation. Source: Microsoft SQL Server Native Client 11.0 SQL State: 42000 Native Error: 5075
1: ADO Error: Number: -2147217900 Description: CREATE DATABASE failed. The default collation of database 'SQLdmRepository' cannot be set to 'SQL_Latin1_General_CP1_CS_AS'. Source: Microsoft SQL Server Native Client 11.0 SQL State: 42000 Native Error: 1806
1: There was a SQL scripting error at line 71. Aborting the setup.
MSI (s) (94!24) [11:41:58:831]: Product: IDERA SQL Diagnostic Manager (x64) -- Error 27506.Error executing SQL script SQLdmDatabaseInstall.sql. Line 71. CREATE DATABASE failed. The default collation of database 'SQLdmRepository' cannot be set to 'SQL_Latin1_General_CP1_CS_AS'. (1806)

It would be nice if the installer gave some hint as to the problem!  The ReverseMojibake() UDF mentioned above is a little unusual: it reverses mangled Unicode to try to get back to the original accented characters, so it includes lots of non-ASCII characters in REPLACE() functions.  However, non-ASCII characters are hardly a new thing!  It's hard to believe that such could break the installer.

Any idea what might be going on?  Are there other places I should look beyond this log file, for clues as to the problem?

Thank you.


Here's the log file, if relevant:

InstallSQLDM.log

Parents
  • The collation mentioned is the default and should work. Here's a screenshot of my repository database.

    The part of the error message that stands out to me is the mention of "ReverseMojibake". This is the first time I've seen this. That's probably what's breaking it. I know that we have problems with triggers when the database is being created so it isn't that much of a stretch that the UDF could cause problems.

    If you look in the installation kit directory (e.g. C:\Program Files\IDERA\SQLdm x64 Installation Kit\Scripts), there's a folder name Scripts. In there, you can find a SQL script that is used to create/upgrade the repository database. The file should be named similar to SQLdmDatabaseInstall_<version_string>.sqlYou can try manually creating the repository using this SQL script but be sure to follow the instructions at the top of the script.

  • ReverseMojibake() is one of my UDFs.  It's in all of the databases, including model.  If DM has a requirement that the model database not include UDFs, it should say so during installation.  Alternatively, just delete UDFs after creating the new database.  This is hardly a rare edge case!

    After deleting the UDF from model, DM installs.  Unfortunately, most of the buttons aren't visible in the following Manage Servers dialog, so I don't know that I will be able to use it:

    Several buttons are obscured; only VM Configuration, OK, and Cancel and visible and enabled

Reply
  • ReverseMojibake() is one of my UDFs.  It's in all of the databases, including model.  If DM has a requirement that the model database not include UDFs, it should say so during installation.  Alternatively, just delete UDFs after creating the new database.  This is hardly a rare edge case!

    After deleting the UDF from model, DM installs.  Unfortunately, most of the buttons aren't visible in the following Manage Servers dialog, so I don't know that I will be able to use it:

    Several buttons are obscured; only VM Configuration, OK, and Cancel and visible and enabled

Children
  • Check your display settings. Different versions of Windows shows the option a little differently but there should be some option that allows you to adjust the text size. If this setting is set to anything above 100%, you'll encounter the problems shown in your screenshot.

    It's my understanding that the upcoming version of SQLDM will be able to support percentages larger than 100%. Until that release is available, you'll have to scale the text size down to 100% otherwise you'll encounter a number of display anomalies.