SQL Server Performance

Windows account super slow

Discussion in 'General DBA Questions' started by HowardG, Sep 19, 2004.

  1. HowardG New Member

    Greetings all.

    I have a fairly simple stored procedure that runs on server A, joins with data on server B, and inserts this into a table back on server A. Running in Query Analyzer logged in as an SQLServer account, the job runs in roughly 1 minute. When I log into QA as a windows account, the same job takes nearly an hour to run.

    Anyone have a clue as to what might be going on there or where I should look?

    I assume if it were some odd permissions problem then it would either run or not run, not just take longer.

    SQLServer 8.00.760 (SP3) on Windows NT 5.0 (2195)


    Thanks.

    HG
  2. derrickleggett New Member

    Try to log in as the account SQL Server is actually running under and see what kind of speed that gives you.

    MeanOldDBA
    derrickleggett@hotmail.com

    When life gives you a lemon, fire the DBA.
  3. satya Moderator

    Also you can monitor the event by using PROFILER for assessment.

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  4. Argyle New Member

    Check that name resolution works without delay on both system and that both servers can access the domain controllers without delays as well.
  5. HowardG New Member

    This may be OT, but how do I check name resolution and domain controller delays? We don't see symptoms of delays in other areas, however, based on you domain controller suggestion, I found this article at MS
    http://support.microsoft.com/default.aspx?scid=kb;en-us;820788&Product=sql2k
    which seems pretty much on target (Delayed Domain Authentication may cause SQL server to Stop Responding). I just don't know how to prove that's the case.

    Thanks.
  6. satya Moderator

    As mentioned in the KBA:
    This problem occurs because of unusually slow domain authentication requests. Therefore, you can avoid this problem by addressing the root cause of the domain authentication performance problem. You can switch to a network library other than TCP/IP, such as Named Pipes, to work around the problem. You can use Client Network Utility to select a preferred network library on a client computer.

    Verify this with your Network Admin in order to get accurate status on network side.
    Ensure


    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.

Share This Page