ca.portal.admin

Re:Different flavors of relational database

Discussion created by ca.portal.admin on May 2, 2006
We did a comparison retrieval between IDMS/SQL (on the mainframe) and
SQL Server (on a Windows server). A database was defined the same way
on both, and loaded with the same data. Queries that used keys (index
or calc) had about the same response time on both. But queries that
generated an area sweep ran noticeably faster on SQL Server, for example
1 second vs. 15 seconds. I am trying to figure out why such a big
difference.

I did not consider the response time for area sweep unreasonable for the
size of the database. But the programmer insisted that it was, and
proved his point with the SQL Server demo. I considered these queries
to be large (for online access), but the SQL Server DBA said that they
are considered small by SQL Server standards. They reported that DB2
(on AIX) could also do similarly large queries with subsecond response
time.

I do realize that there are many differences between the environments,
i.e. hardware, software, operating system, DASD, number of users, etc.
But is there something inherently different about IDMS/SQL that would
cause large queries (area sweeps) to run so much slower than the other
two relational databases?

If anyone else has done similar comparison testing, would you be willing
to share your results?

Kay Rozeboom
State of Iowa
Information Technology Enterprise
Department of Administrative Services
Telephone: 515.281.6139 Fax: 515.281.6137
Email: Kay.Rozeboom@Iowa.Gov
Notice of Confidentiality:
**This E-mail and any of its attachments may contain Lincoln National
Corporation proprietary information, which is privileged, confidential,
or subject to copyright belonging to the Lincoln National Corporation
family of companies. This E-mail is intended solely for the use of the
individual or entity to which it is addressed.
If you are not the intended recipient of this E-mail, you are hereby
notified that any dissemination, distribution, copying, or action taken
in relation to the contents of and attachments to this E-mail is
strictly prohibited and may be unlawful. If you have received this
E-mail in error, please notify the sender immediately and permanently
delete the original and any copy of this E-mail and any printout. Thank
You.**

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








Normal

Normal
New DCMT feature - R16 SP2
"I just noticed that ""DCMT DISPLAY STATISTICS SYSTEM"" now gives current
and HWM totals for users signed on. Cool.
What I did in the past was display all the LTE's and count them. Not
fun on a busy CV.

Kay Rozeboom
State of Iowa
Information Technology Enterprise
Department of Administrative Services
Telephone: 515.281.6139 Fax: 515.281.6137
Email: Kay.Rozeboom@Iowa.Gov

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








Normal

Normal
Weird IDD behavior
"This has happened to me a number of times here, but nowhere else.

I go into the IDD and ADD an element.

IDD 16.0 NO ERRORS
ADD
ELEMENT NAME IS REMINDER-NOTICE-CNT
PUBLIC ACCESS IS ALLOWED FOR ALL
PRIMARY
PICTURE IS 9(05)
.

Then I REPL a record with new element and the element has disappeared!
It seems to take a minute or two for this to happen.

000044 RECORD ELEMENT IS REMINDER-NOTICE-CNT V 1.
000044*+ E DC601012 ELEMENT IS NOT IN DICTIONARY
000044*+ W DC601017 FORWARD SPACING TO NEXT PERIOD

The only way I seem to get the element to stay, is to restrict access to
me only.

Tim Gortner
Sr. Consultant - Sogeti USA LLC
Iowa Department of Human Services
DDM Medical Systems and Data Warehousing
(515) 725-1196

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








Normal

Normal
Re: Weird IDD behavior
"Tim,
Take a look at your default options for VERSION. I seem to remember
something like this once when a contractor set the default version
number to zero instead of one.

Outcomes