A new client recently upgraded from iMIS 10.6 to 15.2.5. During the upgrade, I discovered that the database is case-sensitive. Apparently this collation setting is creating problems in the new version of iMIS. For instance, some functions that staff try to perform, such as billing dues, generate an error message stating that iMIS "cannot resolve the collation conflict". I tried to run the ALTER DATABASE command for changing the database collation from SQL_Latin1_General_CP850_BIN (case-sensitive) to SQL_Latin1_General_CP1_CI_AS (case-insensitive). However, SQL throws all kinds of errors saying that numerous objects and columns are "dependent on database collation." Two of these obects were views, which I simply altered to get rid of the "WITH SCHEMABINDING" until the collation could be changed, then put them back. Some of these objects were Functions that I deleted temporarily. Then I ran into a coupe of tables whose columns were dependent of the db schema, after which I got stuck.
Rather than go through all of this hassle, maybe someone out there has a better way. If anyone has a script or methodology for changing the db collation, would you be willing to share it? If you don't know of a better way, do you know how to temporarily remove the schema depedency for columns in a table? The columns are found in the GiftAidClaimDetail table. One is called TaxReclaimAmount and the other is called LabelName. Both of these columns are COMPUTED, which is probably where the schema dependency is coming in.
Thanks for any help you can give.