|
POST
|
No they shouldn't cause any issues.Mainly it just speeds up the querying process, without altering the schema or data. However, recommendation is to always test on a small subset of data before implementing in production environment.
... View more
10-03-2017
09:47 AM
|
1
|
0
|
1800
|
|
POST
|
Take a look at the Versions table in the Database. Most probably you have that version there.
... View more
10-03-2017
09:31 AM
|
1
|
0
|
1815
|
|
POST
|
You should be able to reuse the Replica name... Can you elaborate on the message you get when trying to do so...
... View more
10-03-2017
08:10 AM
|
0
|
3
|
1815
|
|
POST
|
Try copy and pasting the entire path in ArcGIS Pro...like : C:\Users\%user_profile%\AppData\Roaming and then browse further to what you need
... View more
10-02-2017
12:00 PM
|
1
|
0
|
7032
|
|
POST
|
To register the data as Versioned, you need an Exclusive lock on the data. That is, nobody else should be using that data. It seems that the data may be part of a ArcGIS Server Service...so stop the service and then try Registering as Versioned...
... View more
09-29-2017
06:43 AM
|
1
|
0
|
2153
|
|
POST
|
Consider the possibility of having a separate Testing\Development SQL Server instance. That way it would be easier to have updated data on the Testing database, through simple backup\restore whenever needed.
... View more
09-29-2017
05:41 AM
|
2
|
0
|
4648
|
|
POST
|
ArcMap, in general, takes a long time to load (before choosing MXD). Upwards of 1-2 minutes. This itself indicates something is wrong. I know you mentioned that you have tried all the common tricks and tweaks, but it will help if you list what all steps have you tried till now. So that if you missed something, others can chip in..
... View more
09-27-2017
09:03 PM
|
0
|
1
|
3931
|
|
POST
|
That is a good bit of research work done and excellent troubleshooting for someone who is still learning the ropes of SDE. Good job!
... View more
09-27-2017
11:20 AM
|
2
|
0
|
3528
|
|
POST
|
Well, I tried with sample data and it worked for me. Make sure: 1. There are records matching for the Join that you are creating, for the Update to happen (I know this is obvious, but still confirm) 2. You are checking the correct version in ArcMap\ArcCatalog for the updates after executing the SQL.
... View more
09-27-2017
11:13 AM
|
0
|
1
|
1087
|
|
POST
|
Well, only thing I can think of is that I hope the join is valid and has some records matching... I will try to test with a sample data at my end whenever I have some time to test this and get back..
... View more
09-27-2017
10:33 AM
|
0
|
0
|
1087
|
|
POST
|
Try the below and see if this works: EXEC dbo.create_version 'dbo.DEFAULT', 'WMMtoESRI', 2, 1, 'This version contains data pushed from WMM to ESRI';
EXEC dbo.set_current_version 'WMMtoESRI';
EXEC dbo.edit_version 'WMMtoESRI', 1;
MERGE ElectricNetwork.dbo.Regulators_evw
USING WMM_Export.dbo.REGULATOR
ON ElectricNetwork.dbo.Regulators_evw.GUID = WMM_Export.dbo.REGULATOR.wmextVoltageRegulator__GUID_ESR
WHEN MATCHED THEN
UPDATE SET ElectricNetwork.dbo.Regulators_evw.esPhasing = WMM_Export.dbo.REGULATOR.wmPhasing;
EXEC dbo.edit_version 'WMMtoESRI', 2;
... View more
09-27-2017
10:06 AM
|
2
|
4
|
3950
|
|
POST
|
The SQL looks good to me, but check the following links: Update Versioned View with JOIN arcgis 10.3 - Edit default version table view using SQL Server - Geographic Information Systems Stack Exchange Seems to be a known issue in MS SQL Server. So try using MERGE and check as suggested... You will get multiple MS links for same issue, not even related to Esri, for this error...
... View more
09-27-2017
09:39 AM
|
1
|
5
|
3950
|
|
POST
|
Post the complete SQL you are using.. and I hope you changed the below as well WHERE ElectricNetwork.dbo.Regulators.GUID=WMM_Export.dbo.REGULATOR.wmextVoltageRegulator__GUID_ESR
... View more
09-27-2017
09:21 AM
|
0
|
7
|
3950
|
|
POST
|
You seem to be updating the Feature Class directly, which you should never do using SQL... Check this link: Edit versioned data in SQL Server using SQL—Help | ArcGIS Desktop UPDATE ElectricNetwork.dbo.Regulators The bold part should represent your Versioned View name, which is automatically created when you register as versioned a feature class. Check in Views in SQL Server Management Studio. Also you won't need the below: BEGIN TRANSACTION COMMIT; See the link provided for an example...
... View more
09-27-2017
08:50 AM
|
1
|
9
|
3950
|
|
POST
|
You are updating the Feature Class\Table directly? Or the Versioned View for the feature class? UPDATE ElectricNetwork.dbo.Regulators
... View more
09-27-2017
08:38 AM
|
0
|
11
|
3950
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 10-12-2017 12:37 PM | |
| 4 | 06-18-2025 05:53 AM | |
| 1 | 02-19-2025 02:49 AM | |
| 1 | 02-05-2025 09:56 AM | |
| 2 | 12-16-2024 11:02 PM |
| Online Status |
Offline
|
| Date Last Visited |
06-13-2026
06:42 AM
|