Collation Checker

  • Comments posted to this topic are about the item Collation Checker

  • just a small correction.

    this script gave errors on our dev server, because we have dbs with '.' in the name.

    so we had to change the script in the dynamic sqls part so that @dbname changed to '[' + @dbname +']'

    thanks for the script 🙂

    and keep up the good work

  • thanks kselich, I've never seen a database with a . in the name before, so I didn't consider that. I'll make the change on the script.


  • Hi, thanks for the script!!

    I have to keep any database off-line so the script gave me an error

    so i put an additional condition in 2 where clauses relatives to sysdatabase table to avoid the problem:

    'version is not null'

    maybe is not the smartest way but it works...:Whistling:


  • Hi, I've already rated this as excellent, though (adding to what kselic said) surrounding the dbnames with [] is mandatory because you can have dbnames with various issues, like 'REGISTER DATABASE' (contains space...).

    A last couple suggestion:

    1 add to #database_collations_by_column table a column named 'tablename', both in insert and in last select so you can tell not only column name but also in which table it is, to ease searching for problems in a db...

    2 change from varchar(100) to sysname the column type in those #tables...

    But anyway very useful, I've found a few columns that will create problems in some not distant future.



  • Thanks for the suggestions Luigi and Matteo. I'll make the suggested changes. I'll post it later in the week , as the scripts need to be checked by the administrators again before it get republished.


Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply