POST
|
What kind of updates are we looking at? What will be our limitations if we use the 9months old sample file directly, which seems to work with Version 2022.x. Can you share a recent reference file? We upgraded to Version 2022.x today, but plan to upgrade further once we upgrade the ArcGIS Enterprise environment. Any other tip is appreciated.
... View more
04-11-2023
09:01 AM
|
1
|
0
|
1095
|
POST
|
Hi @Ian_Muehlenhaus. Thank you for the prompt response. We upgraded our Insight to Version 2022.1.1.4568 and were able to add the Teradata connector type successfully. We were previously using Version 2021.3.1.4259, which I am assuming didn't support Teradata maybe. I couldn't confirm this as there isn't any info available in archive for Version 2021.x. Archived help
... View more
04-11-2023
01:46 AM
|
1
|
1
|
1117
|
POST
|
Hello, We are trying to connect to a Teradata DB directly from ArcGIS Insights. Tried to follow the steps, but unable to add the connector type successfully. Has anyone tried connecting to Teradata from ArcGIS Insights? If yes, can someone share the dialect.yml and properties.yml files for reference. Any other tips? Teradata Version: 17.10
... View more
04-09-2023
11:48 PM
|
2
|
10
|
1266
|
POST
|
Always had the understanding that ArcSDE\Enterprise gdb does not have reserved words of its own. These are determined by the host RDBMS on which the geodatabase resides. This document for ArcGIS Pro mentions the same: Define fields in tables Additional field name rules and limitations are as follows: Field names cannot contain reserved words, such as all or result. Consult your database management system (DBMS) documentation for additional reserved words.
... View more
01-26-2023
06:52 AM
|
0
|
0
|
382
|
POST
|
Check the Datareader role in SQL Server. An overview of the db_datareader role Database-level roles
... View more
01-16-2023
11:09 PM
|
0
|
0
|
852
|
POST
|
While the frustration of something not working is expected, this is not the official channel of communication with Esri or the way to report a critical Bug for your organization. I would suggest contacting Esri Technical Support and reporting it. How to report a bug in ArcGIS Pro Report Bug For something so critical for your organization's workflow, I would have expected proper testing before migrating to ArcGIS Pro.
... View more
12-14-2022
11:27 PM
|
0
|
0
|
431
|
POST
|
Joining attributes in one table to another Typically, you'll join a table of data to a layer based on the value of a field that can be found in both tables. The name of the field does not have to be the same, but the data type has to be the same; you join numbers to numbers, strings to strings, and so on. You can perform a join with either the Join Data dialog box, accessed by right-clicking a layer in ArcMap, or the Add Join tool. As long and short are both basically numbers, the Join should work fine.
... View more
11-15-2022
09:32 AM
|
0
|
0
|
391
|
POST
|
How To: Re-synch SQL Server logins or users after restoring a database from backup You'll need to create the required logins at the Instance level, before you Re-synch..
... View more
11-15-2022
09:23 AM
|
3
|
0
|
941
|
POST
|
Check if the below helps: Set language and region Install a localized version of ArcGIS Pro
... View more
11-12-2022
05:45 AM
|
0
|
0
|
643
|
POST
|
Enterprise geodatabase size and name limits (archived 10.3.1 link for reference) Size limits Most size limits in a database depend on the DBMS edition and hardware limitations. One exception is the number of fields (columns) supported in a table or feature class; the maximum number is 500. Be aware, though, that depending on the data types, the maximum number of columns in a table could be less than 500. Most database vendors do not recommend creating tables with over 200 columns of any data type. This is the limitation. So if you are close to that many fields, you may be hitting the limitation.
... View more
09-20-2022
07:15 AM
|
0
|
1
|
1099
|
POST
|
When you create a Feature Class using ArcGIS, the Base/Business Table is created with the same name on the db end (servicepoint in your case). When you 'registered as versioned' the same feature class, the Versioned view (servicepoint_evw) and the delta tables (a- & d- tables) are created at that point of time. As already suggested by Marlon below, use the Versioned View to edit using SQL from db end. That is the recommended way to edit from db end.
... View more
08-19-2022
11:22 AM
|
1
|
0
|
936
|
POST
|
Is that Feature Class registered as versioned? How did you update the data from the database end? Which table/view was used to update the data? Is there any domain/subtype applied on that field?
... View more
08-18-2022
08:35 PM
|
1
|
2
|
968
|
POST
|
If editing using SQL is comfortable for you, why not edit the versioned view using SQL, which is supported by Esri as well. https://desktop.arcgis.com/en/arcmap/latest/manage-data/using-sql-with-gdbs/overview-edit-versioned-data-with-sql.htm
... View more
06-22-2022
11:51 AM
|
1
|
1
|
367
|
POST
|
Enable editor tracking Check if this is what you missed:
... View more
06-01-2022
02:06 PM
|
1
|
1
|
291
|
POST
|
Hi. Considering more than 1 user is supposed to work with the data, where do you plan to store the File geodatabase?
... View more
05-12-2022
09:29 PM
|
0
|
3
|
1383
|
Title | Kudos | Posted |
---|---|---|
1 | 11-28-2023 04:07 AM | |
1 | 02-14-2022 02:53 AM | |
1 | 10-27-2020 09:01 PM | |
2 | 11-28-2023 10:19 PM | |
1 | 11-29-2023 09:28 AM |
Online Status |
Offline
|
Date Last Visited |
Thursday
|