Reading here (https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/an-overview-of-attribute-domains.htm) it appears that the field to which a domain is assigned can be of many data types.
So is it shear imagination when I believe I've Esri heard recommend using data type Integer to obtain best possible performance?
in a RDBMS, integers will outperform strings, especially when indexed or searched.
Thanks for the feedback. My intentions were backed.
Indeed, the best design practice is to have your domains as integer fields and create an index on those columns.
Hi Jens... as John already indicated, spot on, performance-wise integer values are strongly recommended. Now then, if planning the migration of a legacy system to a new schema, keep also in mind the impact of changing data types on other supporting applications.
So, and still strongly recommending the use of integers, I also recommend that you ask yourself whether you will need to overhaul some existing integrations and/or reporting engines adjusting them to now using the integer types, and what the cost of this effort may be. (If you are doing the migration for a client, they would appreciate the insight.)
The domain's descriptions can be text for integer fields. Ex:
Code Description1 Yes0 No
Entering data via dropdowns will display the description and save the code value. You'd need to keep in mind what the values represent when working with the data, such as not thinking the actual value is the string 'Yes'.
サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか?無料アカウントを登録してください。
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.