Extended Procs

  • Dave62

    SSCertifiable

    Points: 6221

    Comments posted to this topic are about the item Extended Procs

  • Koen Verbeeck

    SSC Guru

    Points: 258859

    Nice question. Never even heard about it, made me do some research.

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

  • Mr. Kapsicum

    SSCertifiable

    Points: 6128

    easy point. 🙂

  • MarkusB

    SSC-Dedicated

    Points: 37369

    Not sure about this question.

    I think there is no correct answer given, because even the link provided for SQL 2014 says "Topic Status: Some information in this topic is pre-release and subject to change in future releases"

    Since SQL 2014 is not released yet, you can't be sure what will be in it or not. So I would have chosen "None of the above"

    [font="Verdana"]Markus Bohse[/font]

  • Dscheypie

    Default port

    Points: 1484

    MarkusB (10/1/2013)


    Not sure about this question.

    I think there is no correct answer given, because even the link provided for SQL 2014 says "Topic Status: Some information in this topic is pre-release and subject to change in future releases"

    Since SQL 2014 is not released yet, you can't be sure what will be in it or not. So I would have chosen "None of the above"

    No, Markus, Dave62 is right!

    Look at this document:

    http://msdn.microsoft.com/en-us/library/ms143729(v=sql.120).aspx

    There also it is stated that this feature still exists and will be refused in future times. Just look for the key word "XP_API".

    Or did I misunderstand you? You think that because it is pre-release it might change until the official release of SQL Server 2014? Then of course forget my remark above. I myself fought with this detail and decided to ignore it 😉

    Best regards

    Jens-Peter 🙂

    Edit: detail etc.

    ________________________________________________________
    If you set out to do something, something else must be done first.

  • MarkusB

    SSC-Dedicated

    Points: 37369

    Or did I misunderstand you? You think that because it is pre-release it might change until the official release of SQL Server 2014? Then of course forget my remark above.

    That's exactly my point.

    Even though it's not very likely, it might still change before the final release.

    [font="Verdana"]Markus Bohse[/font]

  • Dscheypie

    Default port

    Points: 1484

    Yes, that's correct. A better answer could have been "... is actually planned to be implemented in SQL Server 2014 ..."

    Jens-Peter 🙂

    ________________________________________________________
    If you set out to do something, something else must be done first.

  • This was removed by the editor as SPAM

  • Carlo Romagnano

    SSC-Insane

    Points: 21665

    I think that extended procedures are unremovable, also, if Microsoft discourages their use.

  • Ed Wagner

    SSC Guru

    Points: 286950

    Good question. I had to research it as well, but never found anything conclusive either way. It came down to a guess between the last 2 and I got it right. I was leaning that way because I had a hard time seeing MS remove something that's so core to SQL Server as a type of OS within the actual OS. Granted, they've done it before.

  • sknox

    SSChampion

    Points: 12200

    Haven't had time to research SQL 2014 yet.

    Guessed optimistically.

    Got it wrong.

    Can anyone explain why this should still be around when CLR has been available to replace its functionality since 2005?

  • Dana Medley

    SSCertifiable

    Points: 6764

    Koen Verbeeck (9/30/2013)


    Nice question. Never even heard about it, made me do some research.

    +1 Good question. Never really used these, so it was good to do some research on it.



    Everything is awesome!

  • Carlo Romagnano

    SSC-Insane

    Points: 21665

    sknox (10/1/2013)


    Haven't had time to research SQL 2014 yet.

    Guessed optimistically.

    Got it wrong.

    Can anyone explain why this should still be around when CLR has been available to replace its functionality since 2005?

    Because of performance! CLR is very dangerous: bad written code can waste cpu time and memory resource.

  • PChiragS

    SSCarpal Tunnel

    Points: 4965

    nice question Dave62..

  • sknox

    SSChampion

    Points: 12200

    Carlo Romagnano (10/1/2013)


    sknox (10/1/2013)


    Haven't had time to research SQL 2014 yet.

    Guessed optimistically.

    Got it wrong.

    Can anyone explain why this should still be around when CLR has been available to replace its functionality since 2005?

    Because of performance! CLR is very dangerous: bad written code can waste cpu time and memory resource.

    And XPs can't!? :crazy:

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

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