<?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 User permissions on SDE stored procedure SQL Server in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/user-permissions-on-sde-stored-procedure-sql/m-p/442799#M25241</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi guys,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I do not like the fact that public role has 'execute' permission on sde system stored procedures because it potentially allows (correct me if I'm wrong) to mess around sde system tables for a user that has only select permissions on all tables (sde and gdb included).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Are all permissions really necessary or the default configuration is a bit generous (for example default permissions on GDB tables are redundant for a geodatabase reader) ? Is there a minimum subset of stored procedures which is really necessary for a database reader ? &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any workaround ?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Alberto&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 28 Jul 2011 15:05:42 GMT</pubDate>
    <dc:creator>AlbertoAloe</dc:creator>
    <dc:date>2011-07-28T15:05:42Z</dc:date>
    <item>
      <title>User permissions on SDE stored procedure SQL Server</title>
      <link>https://community.esri.com/t5/data-management-questions/user-permissions-on-sde-stored-procedure-sql/m-p/442799#M25241</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi guys,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I do not like the fact that public role has 'execute' permission on sde system stored procedures because it potentially allows (correct me if I'm wrong) to mess around sde system tables for a user that has only select permissions on all tables (sde and gdb included).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Are all permissions really necessary or the default configuration is a bit generous (for example default permissions on GDB tables are redundant for a geodatabase reader) ? Is there a minimum subset of stored procedures which is really necessary for a database reader ? &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any workaround ?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Alberto&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jul 2011 15:05:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/user-permissions-on-sde-stored-procedure-sql/m-p/442799#M25241</guid>
      <dc:creator>AlbertoAloe</dc:creator>
      <dc:date>2011-07-28T15:05:42Z</dc:date>
    </item>
  </channel>
</rss>

