It's all about the answers!

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

×1,305

question asked: Jul 09 '10, 2:58 a.m.
question was seen: 5,693 times
last updated: Jul 09 '10, 2:58 a.m.

Related questions

RAM 7.2.0.1 + SQL Server 2008 collator question...

0
Andy Rutherford (21●12●8) | asked Jul 09 '10, 2:58 a.m.
Hi,

A customer of mine is trying to install RAM 7.2.0.1 with SQL Server 2008. The only documentation for installing RAM + SQL Server refers to SQL Server 2005 and not 2008.

The main question they had was about documentation - http://publib.boulder.ibm.com/infocenter/ramhelp/v7r2m0/index.jsp?topic=/com.ibm.ram.installguide.doc/topics/configuring_SQL2005.html

that states using "collation Latin1_General_BIN2" which is correct for SQL Server 2005, but I think this has changed in SQL Server 2008 to Latin1_General_100_BIN2.

Does the customer simply use this new collation setting when installing RAM and SQL Server 2008? Are there any other SQL Server 2008 changes that they should consider, or is there any updated RAM documentation when installing on SQL Server 2008?

thanks

Andy

4 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Rich Kulp (3.6k●3●8) | answered Jul 09 '10, 10:13 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
Hi,

I believe the support documentation, which is outside the install guide,
says we support 2008 for 7201. There have been no changes. The big
requirement for the RAM database is that it be some _BIN2 collation. If
it has been renamed that should be OK. The main reason is that the
non-BIN2 collations sorted in an ignore case manner. This caused
problems. RAM required sort in case sensitive manner. Since we write
everything in Unicode the Latin1_..._BIN2 is usually sufficient.

Rich
0
permanent link
Andy Rutherford (21●12●8) | answered Jul 12 '10, 12:37 a.m.
Hi,

I believe the support documentation, which is outside the install guide,
says we support 2008 for 7201. There have been no changes. The big
requirement for the RAM database is that it be some _BIN2 collation. If
it has been renamed that should be OK. The main reason is that the
non-BIN2 collations sorted in an ignore case manner. This caused
problems. RAM required sort in case sensitive manner. Since we write
everything in Unicode the Latin1_..._BIN2 is usually sufficient.

Rich


Hi Rich,

Thanks for your quick response. If there are no changes, I take it customers don't need to alter the two RAM SQL files that create the DB structures (RAMSCHEMA_SQLServer.sql and bootStrap_SQLServer.sql) in any way before executing them against a SQL Server 2008 instance?

thanks

Andy
0
permanent link
Rich Kulp (3.6k●3●8) | answered Jul 12 '10, 12:40 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Hi,

Since I wrote those two files, I think I would know if they needed to be
changed. :-) They weren't changed when we added Sql Server 2008.

Rich
0
permanent link
Andy Rutherford (21●12●8) | answered Jul 12 '10, 8:18 p.m.
Hi,

Since I wrote those two files, I think I would know if they needed to be
changed. :-) They weren't changed when we added Sql Server 2008.

Rich


Many thanks Rich

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.