topic Re: Any issues deleting a single feature w/ SQL rather than SDE API? in Data Management Questions https://community.esri.com/t5/data-management-questions/any-issues-deleting-a-single-feature-w-sql-rather/m-p/340513#M19375 <HTML><HEAD></HEAD><BODY><SPAN>There's a lot a variables to be resolved before a simple "No" can be given.</SPAN><BR /><SPAN> </SPAN><BR /><SPAN>Is the table versioned?</SPAN><BR /><SPAN> </SPAN><BR /><SPAN>Does the table participate in geodatabase topologies, networks, or object behaviors?</SPAN><BR /><SPAN> </SPAN><BR /><SPAN>Does the layer use SDEBINARY/SDELOB storage?&nbsp; If so, is it in LOAD_ONLY I/O mode?</SPAN><BR /><SPAN> </SPAN><BR /><SPAN>In general, there are triggers to maintain referential integrity, but any of the above</SPAN><BR /><SPAN>could preclude the safe use of DELETE.&nbsp; Note that the same problems would exist</SPAN><BR /><SPAN>if you used the ArcSDE API (SE_stream_delete_from_table is just a wrapper on</SPAN><BR /><SPAN>a SQL delete), but the I/O mode problem would probably be caught at the API.</SPAN><BR /><SPAN> </SPAN><BR /><SPAN>- V</SPAN></BODY></HTML> Mon, 21 Mar 2011 16:50:16 GMT VinceAngelo 2011-03-21T16:50:16Z Any issues deleting a single feature w/ SQL rather than SDE API? https://community.esri.com/t5/data-management-questions/any-issues-deleting-a-single-feature-w-sql-rather/m-p/340512#M19374 <HTML><HEAD></HEAD><BODY><SPAN>Are there any known issues with deleting a feature/row from an SDE feature class with a straight DB 'delete' SQL command, outside of the SDE API?&nbsp; Would that leave any SDE artifacts around that we don't want?</SPAN></BODY></HTML> Mon, 21 Mar 2011 16:32:11 GMT https://community.esri.com/t5/data-management-questions/any-issues-deleting-a-single-feature-w-sql-rather/m-p/340512#M19374 ChristinaKepler 2011-03-21T16:32:11Z Re: Any issues deleting a single feature w/ SQL rather than SDE API? https://community.esri.com/t5/data-management-questions/any-issues-deleting-a-single-feature-w-sql-rather/m-p/340513#M19375 <HTML><HEAD></HEAD><BODY><SPAN>There's a lot a variables to be resolved before a simple "No" can be given.</SPAN><BR /><SPAN> </SPAN><BR /><SPAN>Is the table versioned?</SPAN><BR /><SPAN> </SPAN><BR /><SPAN>Does the table participate in geodatabase topologies, networks, or object behaviors?</SPAN><BR /><SPAN> </SPAN><BR /><SPAN>Does the layer use SDEBINARY/SDELOB storage?&nbsp; If so, is it in LOAD_ONLY I/O mode?</SPAN><BR /><SPAN> </SPAN><BR /><SPAN>In general, there are triggers to maintain referential integrity, but any of the above</SPAN><BR /><SPAN>could preclude the safe use of DELETE.&nbsp; Note that the same problems would exist</SPAN><BR /><SPAN>if you used the ArcSDE API (SE_stream_delete_from_table is just a wrapper on</SPAN><BR /><SPAN>a SQL delete), but the I/O mode problem would probably be caught at the API.</SPAN><BR /><SPAN> </SPAN><BR /><SPAN>- V</SPAN></BODY></HTML> Mon, 21 Mar 2011 16:50:16 GMT https://community.esri.com/t5/data-management-questions/any-issues-deleting-a-single-feature-w-sql-rather/m-p/340513#M19375 VinceAngelo 2011-03-21T16:50:16Z