Get Data Moving 1
Results 1 to 4 of 4

Thread: Minimal Permissions for users to run SQL CDC logger and Attunity Stream

  1. #1
    Maksim Golovkin is offline Junior Member
    Join Date
    Feb 2007
    Location
    Moscow/Kaluga
    Age
    35
    Posts
    6
    Rep Power
    0

    Exclamation Minimal Permissions for users to run SQL CDC logger and Attunity Stream

    I tried to install sqlcdclgr service to execute under unprivileged user and got the following error message: "User 'Attunity' does not have permissions to run DBCC log". User 'Attunity' is NTLM record and flag useWindowsAuth
    What minimal permissions on SQL Server and operating system must have this user for correct work of Attunity Stream?
    The same question about user that is specified up while Implement CDC solution on "Data Source" step.

    Here is configuration of sqlcdclgr service:
    Code:
    <serviceConfig>
        <cdcOrigin server='SMARTSQL' database='CashOffice' user='' password='' useWindowsAuthentication='true' defaultOwner='dbo'/>
        <transientStorage directory='C:\sql_cdc\transient_storage' maxFileSize='1000000' totalSize='100000000' lowThreshold='65' highThreshold='85'/>
        <logging directory='C:\sql_cdc'/>
        <control batchSize='50000' retryInterval='1' debugLevel='none' traceDBCC='false' traceStatistics='false' />
        <detainer detainingTimeInterval='300' detainerTxnDurationLimit='2147483647' traceActivity='false'/>
    </serviceConfig>
    Data Integration Consultant
    S&T International, Moscow, Russia

  2. #2
    Hillel is offline Developer
    Join Date
    Sep 2006
    Posts
    16
    Rep Power
    0

    DB permission required for SQL-CDC LGR service

    Documentation states that:
    "The logon setups should be entered in a way that allows the Attunity Services to access the SQL Server database."
    .
    However - LGR issues those special DBCC calls that require user permissions to default to members of the sysadmin fixed server role or the db_owner fixed database role (at least).
    .
    Regarding the front end - it should be permitted in a manner that allows access to data + metadata - much like the companion MSSQLODBC driver iteself.
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

  3. #3
    Maksim Golovkin is offline Junior Member
    Join Date
    Feb 2007
    Location
    Moscow/Kaluga
    Age
    35
    Posts
    6
    Rep Power
    0
    After I revoked 'System Administrator' server role from user 'Attunity' on SQL Server, granted 'db_owner' and 'public' privileges to the user, and restarted sqlcdclogger service error messages started to appear in cdclogger log as you can see below:
    Code:
    DB-LIBRARY error: General SQL Server error: Check messages from the SQL Server. severity=5
    <<20070703-162416>>	Module:SQLCDC_SESSION/Line:394	MSG_HANDLER captured message:
    	
    SQL Server message 2571, state 1, severity 14:
    	User 'Attunity' does not have permission to run DBCC log.
    Data Integration Consultant
    S&T International, Moscow, Russia

  4. #4
    Hillel is offline Developer
    Join Date
    Sep 2006
    Posts
    16
    Rep Power
    0

    Grant LGR user with SYSADMIN permissions

    A deepr look into this issue yields that, for that specific DBCC call, sysadmin permissions are required.
    Therfore - LGR service input parameters should specify a user which is granted with sysadmin permissions.
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

LinkBacks (?)

  1. 09-18-2008, 06:17 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •