Changing collation on user's db during SQL db setup
![]()
One of our POC customer has concerns on one of the instruction step to set up SQL server 2005 for RQM, and reject to follow the step until we have an explaination on his concerns. The following are details:
Following the menu to set up SQL server 2005 for RQM, one of the step is to change the collation of the Jazz Team Server database, the DBA From the command line, type: ALTER DATABASE jazz COLLATE SQL_Latin1_General_CP437_CS_AS GO The Customer's DBA's responses: "This is a very bad idea. This changes the collation only for the database and not for the underlying objects. It will also leave it in a state where it doesn't match with the TEMPDB on the server and potentially cause issues when doing comparisons. " What is the explaination to his concern to ensure that this command is not going to harm his database. Thanks for your help. This is a POC case, we need to get back to the customer ASAP. Thanks. |
2 answers
![]() One of our POC customer has concerns on one of the instruction step to set up SQL server 2005 for RQM, and reject to follow the step until we have an explaination on his concerns. The following are details: RTC/Jazz requires case-sensitivity in the database and the default collation for Sql Server is a case insensitive collation. We check for this upon startup and will not run if we find that the db is not supporting case sensitivity. That said the collation can be anything that supports case sensitivity. The collation can be set in Sql Server either at the system level making the default for all databases in that system be that or it can be set on an individual database within a system. Either way should work. |
![]()
Hi every one
I have the same problem, the customer position for the database collation, they use the SQL_Latin1_General_CP1_CI_AS collation i dont know if this collation is valid for RQM 2.0.1 We need urgently respond about if this a valid collation thank in advance for your help |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.