AnsweredAssumed Answered

SDE instance copy

Question asked by sizige on Jan 16, 2018
Latest reply on Jan 16, 2018 by jstrahan

Yesterday I was trying to isolate my parcel fabric SDE database, and actually copied the instance to another virtual server.  When noticing that it was my version and that it still showed that I could reconcile and post my updates, I had expected that I created a one or two way replication.  As this was a test environment I continued to edit in the isolated database.  After I saved my edits I went to the original database with my administrative account and there was no replica created.  Yet all my edits showed up, and no rec-post was performed.  So some how, even though I was on a different server, I was still editing directly to the original SDE database.

 

One thing that was quite noticeable is that the file performance increased at its new location.

screen capture of copied SDE instance.

 

 

In ARC Map, how the data set looks.  It still points to original SDE database.

So now I have many questions.

1) Having this as a connected instance to the original, what is happening behind the scenes? 

         Will this cause problems later on in the database?

         How is it still passing information across between vertical servers, when there isn't a replication?

2) How will this affect the version, and versioning environment.

         Should the copied database instance be removed before compress, when other versions are removed?

2) Is this a valid work flow, as the performance dramatically increased?

          

I am not in our IT department, and do not have control of the of the SQL Server manager to look at the system tables. I am however one of the DBO admins for the database, and control operations through ArcCatalog. It was quite a shock on Friday when all this was going on.  Had me thinking about it all weekend.  So any insights on this would be greatly appreciated.

Outcomes