<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic SDE Connections and Locks in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/sde-connections-and-locks/m-p/554095#M31385</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;We have an 10.1 SDE setup with SQL Server.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;It has been setup with Database Authentication Type.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;All ArcGIS users access the database through this connection.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;All database feature class locks show up as being in use by this master connection user, (not the actual user who is accessing it).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We have some people telling us this is best practice and others saying this is a security concern as everyone has the same permissions and there is no way to see who is accessing what.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We need to be able to see sde locks by user, and also need to be able to setup sde groups and user based permissions to feature classes.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Can anyone offer advice?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 24 Feb 2014 13:24:52 GMT</pubDate>
    <dc:creator>bartbart</dc:creator>
    <dc:date>2014-02-24T13:24:52Z</dc:date>
    <item>
      <title>SDE Connections and Locks</title>
      <link>https://community.esri.com/t5/data-management-questions/sde-connections-and-locks/m-p/554095#M31385</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;We have an 10.1 SDE setup with SQL Server.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;It has been setup with Database Authentication Type.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;All ArcGIS users access the database through this connection.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;All database feature class locks show up as being in use by this master connection user, (not the actual user who is accessing it).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We have some people telling us this is best practice and others saying this is a security concern as everyone has the same permissions and there is no way to see who is accessing what.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We need to be able to see sde locks by user, and also need to be able to setup sde groups and user based permissions to feature classes.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Can anyone offer advice?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Feb 2014 13:24:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/sde-connections-and-locks/m-p/554095#M31385</guid>
      <dc:creator>bartbart</dc:creator>
      <dc:date>2014-02-24T13:24:52Z</dc:date>
    </item>
    <item>
      <title>Re: SDE Connections and Locks</title>
      <link>https://community.esri.com/t5/data-management-questions/sde-connections-and-locks/m-p/554096#M31386</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;While common, it is far from best practice to have all users connect as a single login.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In fact, best practice involves using one or more "ownership" accounts to own institutional&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;table resources (feature datasets), using individual user logins to access the geodatabase,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;and making use of roles to assign access to tables by users.&amp;nbsp; Not only does this practice&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;reduce contention to shared resources, it also helps identify who is acessing what, and when.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Note that the RDBMS implements the security model, not ArcSDE (there is no such thing as&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;an "sde group").&amp;nbsp; This is just proper use of the RDBMS' own security model.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Feb 2014 13:49:01 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/sde-connections-and-locks/m-p/554096#M31386</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2014-02-24T13:49:01Z</dc:date>
    </item>
  </channel>
</rss>

