ca.portal.admin

Re: Specifying DBname for SQL-defined databases

Discussion created by ca.portal.admin on Dec 21, 2006
one thought on DBNAMEs - there was at one time (and perhaps still
is) a defined sequence to segment searching
is it alphabetical? is it order added to the DBNAME? I do not remember -
but it is a consideration when modifying DBNAMEs

at least the bind counts are added back to the DCMT D DBNAME command so
you can see how is getting hit the most


Chris Hoelscher
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Specifying DBname for SQL-defined databases
">one thought on DBNAMEs - there was at one time (and perhaps still
is) a defined sequence to segment searching
is it alphabetical? is it order added to the DBNAME? I do not
remember - but it is a consideration when modifying DBNAMEs

at least the bind counts are added back to the DCMT D DBNAME command
so you can see how is getting hit the most


Chris Hoelscher
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Specifying DBname for SQL-defined databases
"Kay - we had a similar problem (re: SQL) and solved it as you described
basically - although with a bit of a twist for local conditions. We have
had no adverse ""logical"" effects in terms of everything works fine. We
have implemented the new DBNAMEs in all environments including
Production. We have not yet started using the new DBNAMEs in Production
- so I can't comment on performance impact - but I wouldn't expect any.

There is an added benefit if you use SQL together with CA-Server via
TCP/IP - you can specify the DBNAME on the connection URL like this:

jdbc:idms://111.222.333.444:99999/JISDCPY0 - where JISDCPY0 is the
dictionary and all application database segments for one physical
instance - and JISDCPY1 is the DBNAME for the same dictionary and a
different physical instance of the same application databases.

From our point of view this is terrific because our mid-range
applications (in development and training) have only ever been able to
access one physical instance and not the other - we see this as a bonus
for using the current version of SQL and Server.

HTH - cheers - Gary

Merry Christmas everybody !

Outcomes