It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,877
×7,469
×5,939
×4,318
×1,590
×1,435
×1,298
×1

question asked: May 15 '22, 11:25 a.m.
question was seen: 1,604 times
last updated: May 17 '22, 2:26 p.m.

Related questions

Connect ELM702 to MSSQL Server 2008

0
Sean F (1.3k●2●52●162) | asked May 15 '22, 11:25 a.m.
edited May 15 '22, 11:26 a.m.

I am trying to connect a ELM702 installation to MSSQL Server 2008 in a test environment

ELM702 officially requires MSSQL2016 or 2017 or 2019

It installs and runs on many unsupported platforms (e.g. Win11, WinServer2008) with only minor warning messages


But trying to connect to an unsupported version of MSSQL generates an explicit  blocker.

The startup wizard runs and successfully connects to the server with the MSSQL driver sqljdbc42.jar OK and the Create Table button appears

But when I hit 'Create Tables' I get the error

The "com.ibm.team.repository.service.internal.schemagen.PersistentMappingService" feature could not start. (com.ibm.team.repository.common.transport.TeamServiceRegistryException)ID CRJAZ1092E
Caused by:
The system schema could not be created. (java.lang.RuntimeException)ID CRJAZ0820E
Caused by:
SQL Server 2016 or 2017 or 2019 (13.x or 14.x or 15.x) is required but version "10.50.4000" was detected instead. (com.ibm.team.repository.common.TeamRepositoryException)ID CRJAZ1256I

The is just a temporary dev/test deployment I am trying to create. It is not a production deployment.

Does anybody know if there is a specific reason why the blocker has been implemented by development?

Does anybody know any hacks or ways round the blocker so I can run the product in a test environment with ELM702 hooked up to MSSQL2008 (or any other MSSQL other than 16,17,19)?

Thanks

4 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
David Honey (1.8k●1●7) | answered May 16 '22, 4:50 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Re: Does anybody know if there is a specific reason why the blocker has been implemented by development?

Yes, to prevent/discourage users from using sunsupported database vendor versions!
Product management decides which data vendors and versions are supported in each release. Each additional one requires testing effort. So this is a business decision based on containing test effort.



0
permanent link
David Honey (1.8k●1●7) | answered May 16 '22, 5:29 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

You should also be aware that IBM is encoraging customers to move away from MS SQL Server to either Oracle or DB2 for production environments. I believe there is an intent to drop support for MS SQL Server inb a future release. If you just want to kick the tyres, you can use the built-in Apache database support.

0
permanent link
Paul Ellis (1.3k●6●13) | answered May 16 '22, 8:00 a.m.
JAZZ DEVELOPER
Hi Sean,

There is nothing about your suggestion that makes me feel comfortable.  As David Honey has mentioned, SQL Server struggles with the complex SQL that ELM uses and this has become worse over time.


Although ELM702 officially requires MSSQL2016 or 2017 or 2019, we have seen upgrades on 2016 simply fail to complete: https://www.ibm.com/support/pages/ibm%C2%AE-doors%C2%AE-next-upgrade-6x-7x-sql-server-2016-appears-hang-initialization-complete-phase


So, the simple answer is that there isn't an override here. 
The more pertinent answer is, that you don't want to go there and would be likely to hit more issues and lose more time than it saves you
0
permanent link
Sean F (1.3k●2●52●162) | answered May 17 '22, 2:15 p.m.
edited May 17 '22, 2:26 p.m.

Thanks for your advice and guidance David and Paul.

Yes, I was aware of the MSSQL deprecation plans, thanks.

I am upgrading an RTC database from 406 to 702 and then moving it to a new network.

The upgrade involves 406->407->502->6061->702->702 on New Network (Server Rename)

I was trying to do the upgrade phase (406->702) on a single MSSQL server (which happens to be 2008)

But since that is not possible (the repotools -addTables command also has the explicit version blocker on it) I will deploy additional versions of MSSQL Server.

It looks like 3 versions of MSSQL will be the minimum. MSSQL2008 (for 406 and 407), MSSQL2014 (for CLM502 and 6061) and MSSQL 2017/2019 (for ELM702)

Your answer

Register or to post 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.