|
IDEA
|
@SavageTrimble - Please update this idea to include details if this is specifically for UN datasets to be owned by DBO.
... View more
Monday
|
0
|
0
|
46
|
|
BLOG
|
The Create Database Sequence and Delete Database Sequence tools help to aid in automated workflows where the sequence name is recorded and maintained. For example, when creating an attribute rule where a sequence is used as part of the script expression. You will keep track of the sequence name for these workflows to help reference them directly in your workflows. What if you don't recall the name of the sequence that was created from one of your workflows, or you want to be able to inspect the properties of the existing sequences in the database? Many of you have asked for the ability to view database sequences directly from ArcGIS Pro. 💡Community idea - Ability to view database sequence in ArcGIS Pro Enhancement - ENH-000141842 - Add the ability to view or export database sequences from an enterprise database in streamlined fashion from ArcGIS Pro For FGDB data sources, you can use the ListDatabaseSequences function to get a list of database sequences. This allows you to confirm the sequence name and review sequence properties before creating or deleting database sequences in your geodatabase. What about other data sources, like EGDB? While there is no current tool or UI in ArcGIS Pro to view and manage database sequences for enterprise geodatabases, there are many options available. View and manage database sequences: Use a database client application For enterprise geodatabases there are many 3rd party client applications available to view and manage database sequences directly. Depending on your DBMS platform, the vendor may have a client application that is best suited for working with sequences. For example: SQL Server Management Studio. Dbeaver is also a good multi-platform client application that can be used. Use a Python script With a python script, you can use the ArcSDESQLExecute class to execute SQL statements against an enterprise geodatabase connection and print the sequence name and properties directly in the python window. You can find some example scripts below for specific platforms. Python Script examples SQL Server: import arcpy
# Path to your SDE connection file
sde_conn = r"C:\Users\dak12273\AppData\Local\Temp\ArcGISProTemp29572\Untitled\SQLServer-DevDGD00100-SQLServerTesting.sde"
# SQL query to get sequence names and their schema owners
sql = """
SELECT
CAST(s.name AS varchar(128)) AS SequenceOwner,
CAST(seq.name AS varchar(128)) AS SequenceName,
ISNULL(CONVERT(varchar(100), seq.start_value), '') AS StartValue,
ISNULL(CONVERT(varchar(100), seq.increment), '') AS IncrementValue,
ISNULL(CONVERT(varchar(100), seq.current_value), '') AS CurrentValue
FROM sys.sequences AS seq
JOIN sys.schemas AS s ON seq.schema_id = s.schema_id
ORDER BY s.name, seq.name;
"""
ex = arcpy.ArcSDESQLExecute(sde_conn)
try:
rows = ex.execute(sql)
finally:
try: ex.close()
except: pass
if rows:
# Print header
print(f"{'SequenceOwner':<20}{'SequenceName':<35}{'Start':<10}{'Increment':<12}{'Current':<10}")
print("-" * 90)
# Print rows
for owner, name, start_v, inc_v, cur_v in rows:
print(f"{owner:<20}{name:<35}{start_v:<10}{inc_v:<12}{cur_v:<10}")
else:
print("No sequences found.") Postgresql: import arcpy
# Path to your SDE connection file
sde_conn = r"C:\\Users\\dak12273\\AppData\\Local\\Temp\\ArcGISProTemp29572\\Untitled\\PostgreSQL-DevDGD00100-pg_testing(dakota).sde"
# SQL query to get sequence names and their schema owners
sql = """
SELECT
sequence_name AS SequenceName,
start_value AS StartValue,
increment AS IncrementValue
FROM information_schema.sequences
ORDER BY sequence_name;
"""
ex = arcpy.ArcSDESQLExecute(sde_conn)
try:
rows = ex.execute(sql)
finally:
try: ex.close()
except: pass
if rows:
# Print header
print(f"{'SequenceName':<35}{'Increment':<12}{'StartValue':<10}")
print("-" * 90)
# Print rows
for name, start_v, inc_v in rows:
print(f"{name:<35}{inc_v:<12}{start_v:<10}")
else:
print("No sequences found.") Oracle: import arcpy
# Path to your SDE connection file
sde_conn = "path to your SDE connection file"
# SQL query to get sequence names and their schema owners
sql = """
SELECT
sequence_name AS SequenceName,
min_value AS StartValue,
increment_by AS IncrementValue,
last_number AS CurrentValue
FROM user_sequences
ORDER BY sequence_name;
"""
ex = arcpy.ArcSDESQLExecute(sde_conn)
try:
rows = ex.execute(sql)
finally:
try: ex.close()
except: pass
if rows:
# Print header
print(f"{'SequenceName':<35}{'StartValue':<10}{'Increment':<12}{'Current':<10}")
print("-" * 90)
# Print rows
for name, start_v, inc_v in rows:
print(f"{name:<35}{start_v:<10}{inc_v:<12}{cur_v:<10}")
else:
print("No sequences found.") Mobile GDB: import arcpy
import sqlite3
gdb_path = r"C:\Users\dak12273\AppData\Local\Temp\ArcGISProTemp29572\Untitled\Sequence.geodatabase"
conn = sqlite3.connect(gdb_path)
cur = conn.cursor()
cur.execute("""
SELECT
sequence_name AS SequenceName,
nextval AS NextValue,
increment AS IncrementValue,
starting_point AS StartValue
FROM GDB_Sequences
ORDER BY sequence_name;
""")
rows = cur.fetchall()
# headers
print(f"{'SequenceName':<35}{'NextValue':<12}{'Increment':<12}{'StartValue':<12}")
print("-" * 71)
for seq_name, next_val, inc, start_val in rows:
print(f"{seq_name:<35}{str(next_val):<12}{str(inc):<12}{str(start_val):<12}")
conn.close()
... View more
3 weeks ago
|
4
|
0
|
134
|
|
POST
|
Branch versioned data currently only supports accessing a specific date and time. I am not able to select the Historical Moment radio button like you are showing - it is not enabled in the UI. There is an existing enhancement request you can contact support services to get added to. Please give a justification and explain your workflow in detail where being able to access a historical moment/marker would be beneficial to your organization. ENH-000128422 - Support working with historical markers for feature services with the version management capability.
... View more
11-06-2025
03:32 PM
|
2
|
0
|
187
|
|
POST
|
@rcGIS I was checking back to update the links and see you have already found these! Let us know if you have any questions about how to proceed. What are your plans moving forward? Are you moving to key-pair or will you explore using MFA when working in ArcGIS Pro?
... View more
03-10-2025
06:20 AM
|
0
|
1
|
1636
|
|
POST
|
Most of the versioning editing and administration workflows are similar between the versioning types. It really comes down to if you are wanting more service based editing workflows from a range of client applications. If you are ONLY intending on using ArcGIS Pro and you don't have one of the industry specific data models (UN/TN/parcel fabric), then you can decide what is easier to configure for this project. You can always have a mixture of registration types in your geodatabase. I recommend you give branch a test spin with a few datasets to see. This video from last year's UC has some high level similiaries and differences at the beginning. check out around the 5 minute mark. https://mediaspace.esri.com/media/t/1_6w6jmm4q/309413912
... View more
07-03-2024
06:55 AM
|
1
|
0
|
1684
|
|
IDEA
|
@Bud - After re-reading this I believe there was a misundertanding of the larger scope of this request. It was read as - I only want to see the datasets owned by the 'current' connected user in my database connection. You actually want a way to filter based on a user provided owner (this could be different than the current connected user even). Do you want the filtering done based on the actual owner or the schema (because this can differ).
... View more
06-12-2024
05:48 AM
|
0
|
0
|
2005
|
|
POST
|
Looks like you got some great advice and information. If you check the properties dialog for the table/feature class you can use the value for Data Type. Database means non-geodatabase (or not registered with the geodatabase) Enterprise Geodatabase means it is registered with the geodatabase You'll also notice that for "non-geodatabase objects", you will have the Register With Geodatabase right-click context menu available in the Catalog pane
... View more
02-16-2024
07:09 AM
|
0
|
1
|
2818
|
|
POST
|
Yes it was also included in 2.9.11 and 3.1.4 (not sure why it is not showing this version yet). https://www.esri.com/content/dam/esrisites/en-us/media/products/arcgis-pro-issues-addressed/arcgis-pro-3-1-issues-addressed.pdf
... View more
01-31-2024
01:41 PM
|
0
|
0
|
2534
|
|
POST
|
Looks like this was handled in BUG-000156079 That will be helpful to see where it is fixed in releases and patches.
... View more
01-31-2024
01:28 PM
|
0
|
0
|
2541
|
|
POST
|
The geodatabase team has heard many users voice concerns about this analyzer error blocking publishing when having hidden fields. While this may be problematic in some cases of hidden fields being used in a rule, it is not always the case. The existing analyzer error will become a warning instead.
... View more
01-31-2024
01:16 PM
|
2
|
1
|
2548
|
|
IDEA
|
@-_Ashley-B-Potter_- - Currently the way the UI is designed, the datasource has to be selected to enable the contextual Versioning tab. This sets the active datasource in case you have multiple data sources in your map view. There is an enhancement request to improve this UX by making the tab contextual based on map contents and not activated by having an active data source selection made. ENH-000128750 - In ArcGIS Pro with versioned data the versioning tab should be active automatically Are you saying that you typically work with a map that only has data from one datasource and you want the versioning tab to be automatically enabled and set to the first datasource? What would you expect the UX to be like in the case where there are multiple datasources in the map? This will be helpful for our review. You also have the option to use the Reconcile Versions geoprocessing tool that takes an Input workspace.
... View more
01-02-2024
11:40 AM
|
0
|
0
|
1188
|
|
POST
|
@SamSzotkowski - I sent you a direct message with some questions and I also recommend you reach out to technical support so we can isolate the issue for you and get to the root of the problem. Please feel free to reach out to me directly.
... View more
11-01-2023
06:05 AM
|
0
|
0
|
3847
|
|
POST
|
@gis_grow - I would also like to ask that if you do log an Idea, please include any specific attributes or metrics you are looking to monitor in your SAP HANA Enterprise geodatabase. You can review the existing 'Collected attributes' or 'Collected metrics' in the ArcGIS Monitor documentation for the platforms that are supported: ArcGIS Monitor - Register SQL Server databases ArcGIS Monitor - Register Oracle databases ArcGIS Monitor - Register PostgreSQL databases
... View more
10-10-2023
09:19 AM
|
0
|
0
|
847
|
|
POST
|
Sorry this was not answered by anyone when you originally posted. I found this thread searching and wanted to leave the answer incase someone else has this in the future. You can use the Versions view or the Alter Version geoprocessing tool to change the access property to protected. The default version must have the access changed when directly connected to the source database using a database connection (established as the geodatabase administrator). It is not supported to alter the default version access property via services. https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/manage-branch-versions.htm#GUID-A216B1EB-FEF8-490B-ABB4-C308F00878E3
... View more
02-28-2023
10:35 AM
|
0
|
3
|
2202
|
|
POST
|
For the ArcGIS Enterprise 10.9.1 version, you can only publish Snowflake data from ArcGIS Pro as a map image layer. Editing data in Snowflake is not on the near term horizon, but there are plans to provide support for query only feature services for Snowflake data in an upcoming release. Here is a blog that may be helpful! https://www.esri.com/arcgis-blog/products/arcgis-pro/data-management/introducing-cloud-data-warehouse-support/
... View more
01-13-2023
11:01 AM
|
1
|
0
|
1920
|
| Title | Kudos | Posted |
|---|---|---|
| 4 | 3 weeks ago | |
| 2 | 11-06-2025 03:32 PM | |
| 8 | 05-23-2022 01:34 PM | |
| 1 | 03-24-2022 06:56 AM | |
| 1 | 07-03-2024 06:55 AM |
| Online Status |
Offline
|
| Date Last Visited |
Monday
|