idea Table to Geodatabase — Import text fields as NVARCHAR2, not NCLOB (Oracle) in ArcGIS Pro Ideas

Table to Geodatabase — Import text fields as NVARCHAR2, not NCLOB (Oracle)

Bud — Thu, 26 Dec 2024 18:12:06 GMT

ArcGIS Pro 2.9.5; Oracle 18c 10.7.1 EGDB:

The Table to Geodatabase GP tool imports .CSV text fields as NCLOB (1073741822 characters). That's too many characters.

It would help to have the option to import text fields as NVARCHAR2(255) instead.

https://community.esri.com/t5/arcgis-pro-questions/get-maximum-text-value-length-of-multiple-text/m-p/1552934/highlight/true#M89546

Re: Table to Geodatabase — Import text fields as NVARCHAR2, not NCLOB (Oracle)

DavidSolari — Mon, 28 Oct 2024 20:08:25 GMT

CSV files have an effectively unbound length per field which is why dumping them straight to your EGDB picks that data type. You'd be better off extracting the data to an intermediate table in a File or Mobile Geodatabase where you can clean up the data and schema before loading it into your EGDB. If you're genuinely concerned about database performance you'll want to prep your schemas by hand, then use Append to transform the CSVs into the new format.