Latest Contributions by AsrujitSengupta

Have you tried copying the entire Feature Dataset from the File Geodatabase to the sde Geodatabase? You can Copy/Paste the Geometric Network. That shouldn't be a problem. "The "in_memory" workspace is not supported as the output location." Solution - Confirm that the output location is valid and does not contain any files that will interfere with a successful copy operation. Regards, Asrujit ... View more

If the dataset is registered as versioned, the Insert, Update and Delete privileges must be granted or revoked as a group. The following webhelp mentions the same (at the bottom of the page): What are user privileges? http://resources.arcgis.com/en/help/main/10.1/index.html#//002q0000002r000000 Regards, Asrujit ... View more

Thanks Kimberly, I had overlooked that. The 'Enable Geodatabase" does come up in Workgroup aswell if we are connected through "Add Database Connection", after creating a database using SQL server Management studio! But Rob had used the "Add Database Server" option it seems. The part which confused me was-- that he mentioned that a database had been created in the SQL server Management Studio & that he could connect using Add Database Connection! So rest of my post went accordingly! After re-installing the SQL server, he could create without any problem, so it seems the problem was related to improper installation maybe. ... View more

Sandy, Just like Joe mentioned.....the terminologies that you are using are confusing. If you are talking about SDE.Default version and a child version of the default, in a geodatabase....then NO....the data will not be present in the geodatabase. The confusing bit is......If you are connected to the geodatabase through a CHILD version, and delete the data.....then the data gets deleted from your geodatabase, and not just from that version!!  In this case you won't be able to see the data in the geodatabase even if you connect using the SDE.Default version. If you are talking about PARENT & Child Replica, which involves two different geodatabases.....then the answer is YES ....if the data has been deleted in the Child Geodatabse...the data will still be present in the Parent Geodatabase.... Regards, Asrujit ... View more

Versions are database specific and not data specific. In your case it might be that, the user using the Child Version doesn't have enough privileges to view that Feature Class ... View more

The problem is that, I had sent the Export Message, but the other user was not able to Import the same due to some error in the file. I will try Re-Export Unacknowledged Changes and lets see if that works! Thank you for your reply! ... View more

Well, at the risk of starting a flame war, your use of the phrase  "feature class in a non-sde database" is what threw me.  Any databse I've ever worked with outside of the GeoDataBase realm uses the term record.... Don't worry, its always better to get the doubts cleared. Rather you have a lot more to share, than me. 🙂 Anyways, answering your question, in ArcCatalog, if you just connect to a database created using SQL Server Management studio, it gives you the option to "Create a Feature Class". When you try to edit 'this' feature class in ArcMap, thats when you face the error "The workspace containing this data cannot be edited".....which Rob stated in his first post! You need to Register the Feature Class with Geodatabase, after converting the database into a geodatabase to edit in ArcMap[ATTACH=CONFIG]18345[/ATTACH]! Regards, Asrujit ... View more

What does this mean?  Are you saying that at 10.1 all personal and file based geodatabases are off limits?  I hardly think so... By non-sde database (observe the term 'database' and not 'geodatabase'), I referred to the databases created through the SQL Server Management Studio. These databases do not have the repository tables unless you " Enable Geodatabase..." after connecting through ArcCatalog. The File/Personal are created as 'GEODATABASE' and hence you can edit feature classes etc stored inside them without any problem. I hope I clarified the doubt. Regards, Asrujit ... View more

Desktop 10.0 can write/read data from SDE 10.1, without any problem. The error message would help us to understand better, the problem that you are facing. ... View more

Simply Right Click on the Database Connection in ArcCatalog->Enable Geodatabase... This will create the geodatabase. You can then 'Register with Geodatabase', the existing Feature Classes or create new feature classes. You will now be able to Edit these in ArcMap without any problem. ... View more

ArcGIS Desktop 10.1 does not support editing feature classes of a non-sde database. If you are connecting to the stand alone database (Which does not contain ArcSDE repository tables) you can create, load, view and query the feature class but cannot edit the feature class. In order to edit the feature class you need to be connected to geodatabase (which contains geodatabase tables, functions, and procedures), i.e after creating the database, you need to ENABLE GEODATABASE, to create the Repository Tables, etc which converts the database into a Geodatabase. The below link has more information on this. # Database connections in ArcGIS for Desktop: http://resources.arcgis.com/en/help/main/10.1/index.html#//002q00000031000000 Regards, Asrujit ... View more

"C:\Users\myname\AppData\Roaming\Esri\Desktop10.1\ArcCatalog\GISDATASTORAGE.sde" The above path is the location where the geodatabase connection files for ArcCatalog are stored by default. You can even copy paste the "GISDATASTORAGE.sde" connection file and place it in your desired folder on any drive of your choice and then connect to it from ArcCatalog. ... View more

Check the log files in sdehome\etc....it will give you an idea as to what is preventing you from connecting. ... View more

The point of using the "Register with existing data" options is that the data present in both the geodatabases should be exactly similar. Only then is this option viable. This is the reason we need to create dummy DTs with the same name as the existing DTs, just to create the replica between the two. If you want to avoid creating dummy DTs, simply use the create replica tool, which will automatically create similar DTs in the target geodatabase. ... View more