Post reply

sp_cursoropen

  • April 27, 2008 at 8:31 pm

    #69930

    Recently our server got many blocking issues from users accessing a certain database in the server. By running the sql profiler i got the following commands which "i guess" causing the blocking

    declare @P1 int

    set @P1=180150000

    declare @P2 int

    set @P2=1

    declare @P3 int

    set @P3=16388

    declare @P4 int

    set @P4=50571

    exec sp_cursoropen

    @P1 output,

    N'select * from TABLE_XXX',

    @P2 output,

    @P3 output,

    @P4 output

    select @P1, @P2, @P3, @P4

    Browsing alot of other sites i noticed that they are talking about an ODBC etc connection that is causing the sql server client component to open a cursor. I would like to ask the experts on how to handle/solve this kind of problem blocking usually occurs 4-7 times a week. Thank ouy very much and have a pleasant day

    "-=Still Learning=-"

    Lester Policarpio

  • April 28, 2008 at 7:55 am

    #807773

    Hmm.. how do you guess this code is the problem? Could you try either Activity Monitor (in Enterprise Mgr under Management..Current Activity) or System Monitor (from Admin Tools - Perfomance and select the appropriate MSSQL lock info) if you catch it when running or a trace of the lock events?

    I am no expert but I don't think a select statement would typically cause a block. Then again cursors are a mysterious and costly thing to be using.

    Good luck

  • June 3, 2009 at 10:20 am

    #1004161

    Hi ,

    Guys any information on this problem ?

    I am facing same problem in my DB

    Let me know your information.

    Thanks

    Ichbinraj

  • June 3, 2009 at 1:03 pm

    #1004241

    http://support.microsoft.com/kb/224453

    Thanx.
    Vinay

    http://rdbmsexperts.com/Blogs/
    http://vinay-thakur.spaces.live.com/
    http://twitter.com/ThakurVinay

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply