# Superdescriptor

**URL:** <https://techcommunity.softwareag.com/t/superdescriptor/57974>\
**Category:** Forum\
**Tags:** Adabas-Natural, Adabas, Adabas-Scope-of-Product\
**Created:** [April 26, 2006, 11:23pm UTC](https://techcommunity.softwareag.com/t/superdescriptor/57974 "2006-04-26T23:23:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Richard](https://avatars.discourse-cdn.com/v4/letter/r/f0a364/32.png) [@Richard](https://techcommunity.softwareag.com/u/Richard)\
**Post date:** [April 26, 2006, 11:23pm UTC](https://techcommunity.softwareag.com/t/superdescriptor/57974/1 "2006-04-26T23:23:51Z")

</div>

Hello -

Please refresh my memory. Are there any performance issues that should be considered when defining a SP which contains a field from within a PE?

Thanks,  
Richard

---

<div class="post-metadata">

**Author:** ![Ralph\_Zbrog](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/ralph_zbrog/32/78_2.png) [@Ralph\_Zbrog](https://techcommunity.softwareag.com/u/Ralph_Zbrog)\
**Post date:** [April 28, 2006, 1:04am UTC](https://techcommunity.softwareag.com/t/superdescriptor/57974/2 "2006-04-28T01:04:27Z")

</div>

I don’t think you’ll see a performance hit from an Adabas point of view.

On the programming side, consider that you can’t issue a READ against such a superdescriptor. You could simulate a READ with a HISTOGRAM/FIND combination, but, obviously, this requires additional Adabas commands.

If processing large volumes of data, there could be a performance hit from using FINDs (as compared to READs), with Adabas processing large ISN lists from its WORK dataset.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 2:38pm UTC](https://techcommunity.softwareag.com/t/superdescriptor/57974/3 "2021-04-02T14:38:58Z")

</div>