Case study: Simple solution to tackle Collation linked error when executing some

Many of the software Programs have installation or deployment routines, which inspite of many advancements and refinements in
the GUIs, are used on all sorts of systems.
Sometimes, when calling the routines to run in a batch mode, through Java or other means, we get this error:

Truncated Logs are shared below and I feel these should be well elabrated and used.

INFO   – MSSQL matched
 INFO   – Parsing [./sql/createTables.sql] :
          Connecting to isdb_scanners@jdbc:micros
oft:sqlserver://localhost:1433 as isuser
2016-09-29 18:56:11,367 INFO   – MSSQL parser: Tables found: 31
2016-09-29 18:56:11,378 ERROR  – Fatal error, exitting with [1]
opuslab.util.serverinstaller.SetupException
        at opuslab.util.dbupdate.metadata.MSSQLMetaData.process(MSSQLMetaData.ja
va:52)
        at opuslab.util.dbupdate.DDLCompare.init(DDLCompare.java:67)
        at opuslab.util.dbupdate.ISDBUpdateProcessor.doCompare(ISDBUpdateProcess
or.java:32)
……………………
More will follow this :
at opuslab.util.serverinstaller.Installer.main(Installer.java:165)
To rectify java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Inv
alid object name ‘information_schema.columns’.
at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source
)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
To rectify the same, we can logon to the Sql Server Management studio and connect to the master Db and execute these commands:

ALTER DATABASE isdb_scanners SET SINGLE_USER WITH ROLLBACK IMMEDIATE
go
ALTER DATABASE isdb_scanners COLLATE Latin1_General_CI_AS 
go
ALTER DATABASE isdb_scanners SET MULTI_USER
go

The last command is necessary to bring back the Sql Server to the normal: MULTI USER mode else otherwise it can cause problems.
Collation is a way to specify a broad based behavior such as for case sensitivity, width of characters, multi or single byte characters etc.

Source checked to find solution to the problem: =>
http://www.databasejournal.com/features/mssql/article.php/3302341/SQL-Server-and-Collation.htm
and rest based on own experience