DONEPROC

  • Comments posted to this topic are about the item DONEPROC

  • Never heard of it. Probably will never use it. Misread the documentation and got it wrong.

    Nice question though 😀

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Never heard of it, so I googled. Found this: http://msdn.microsoft.com/en-us/library/dd340753.aspx

    There it says 'CurCmd', not 'CurrCmd'. Apart from that all 5 seem to be correct.

  • F. van Ruyven (10/22/2014)


    There it says 'CurCmd', not 'CurrCmd'. Apart from that all 5 seem to be correct.

    The question said:

    A DONEPROC token is sent for each SQL statements within a stored procedure that has been executed.

    The documentation says:

    A DONEPROC token is sent when all the SQL statements within a stored procedure have been executed.

    This was the part that I misread. 🙂

    Statement number 5 is also incorrect, the data types are not the same.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Same here, never heard about it b4 & I don`t think I will use it in the future, so had 2 do some R&D on it.

    Thanx 🙂

    Thanks & Best Regards,
    Hany Helmy
    SQL Server Database Consultant

  • Quite frankly: If you think you have to know this, you're very likely doing something wrong. Still, I've earned yet another very arcane bragging point.:hehe:


    Just because you're right doesn't mean everybody else is wrong.

  • Thank you for the post, really eye opening.. And really had no idea what this was.

    I read it and without any research, i selected the choice and got it wrong. Just out of curiousity, how where and when we are suppose to use this? Any example available?:-)

    ww; Raghu
    --
    The first and the hardest SQL statement I have wrote- "select * from customers" - and I was happy and felt smart.

  • Well, if you don't like any of the available clients API:s, or if you're implementing SQL Server support on a new platform, you're going to have to know this very well. Otherwise, not so much...


    Just because you're right doesn't mean everybody else is wrong.

  • Raghavendra Mudugal (10/22/2014)


    Thank you for the post, really eye opening.. And really had no idea what this was.

    I read it and without any research, i selected the choice and got it wrong. Just out of curiousity, how where and when we are suppose to use this? Any example available?:-)

    I have already included a use case in the form of api request in the answer:

    http://pekim.github.io/tedious/api-request.html

    I hope the following link can shed more light on use on use of tokens in packet data streams.

    http://msdn.microsoft.com/en-us/library/dd341450.aspx

  • There is a typo in option #4 that caused me to get it wrong.

    4) The Token Stream Definition parameters are TokenType, Status, CurrCmd, DoneRowCount

    I thought the CurrCmd parameter typo was intentional so I didn't select this option.

    For the QotD, it's always so hard to tell.

  • ksatpute123 (10/22/2014)


    Raghavendra Mudugal (10/22/2014)


    Thank you for the post, really eye opening.. And really had no idea what this was.

    I read it and without any research, i selected the choice and got it wrong. Just out of curiousity, how where and when we are suppose to use this? Any example available?:-)

    I have already included a use case in the form of api request in the answer:

    http://pekim.github.io/tedious/api-request.html

    I hope the following link can shed more light on use on use of tokens in packet data streams.

    http://msdn.microsoft.com/en-us/library/dd341450.aspx

    Thanks for the link, actually i saw the use case, but still i dont clearly understand its purpose. Say, NOLOCK, i can understand it usafe and its purpose and its pros and cons.. It kind of give you the clarity, but i am faiiling this to see. I will keep this in mind, in parallel will dig deeper.

    Thank you.

    ww; Raghu
    --
    The first and the hardest SQL statement I have wrote- "select * from customers" - and I was happy and felt smart.

  • Raghavendra Mudugal (10/22/2014)


    ksatpute123 (10/22/2014)


    Raghavendra Mudugal (10/22/2014)


    Thank you for the post, really eye opening.. And really had no idea what this was.

    I read it and without any research, i selected the choice and got it wrong. Just out of curiousity, how where and when we are suppose to use this? Any example available?:-)

    I have already included a use case in the form of api request in the answer:

    http://pekim.github.io/tedious/api-request.html

    I hope the following link can shed more light on use on use of tokens in packet data streams.

    http://msdn.microsoft.com/en-us/library/dd341450.aspx

    Thanks for the link, actually i saw the use case, but still i dont clearly understand its purpose.

    Apparently it is some sort of NodeJS API on top of SQL Server. Whatever that means 😀

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • I had never heard of it either. Read the MSDN page, so I learned something. Like other who have posted here, I'll probably never use it.

  • This was removed by the editor as SPAM

  • New to me too but sounds interesting. I think I'll look into it more. Thanks.

Viewing 15 posts - 1 through 15 (of 24 total)

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