Reference 'Deleted' table: Dynamic SQL

  • I got

    Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows NT 5.2 (Build 3790: Service Pack 2)

    but server is w2k3 R2 Standard Edition.

  • rodney.williams (4/8/2009)


    I got

    Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows NT 5.2 (Build 3790: Service Pack 2)

    Yup, that a SQL 2000 server alright, not only that, it's MSDE (a free, restricted version of the database engine)

    but server is w2k3 R2 Standard Edition.

    The operating system is Server 2003, that can be seen from the last clause of @@version. That makes absolutely no difference to the database engine. The database engine there is SQL 2000. The results of @@version say that clearly - Microsoft SQL Server 2000 - 8.00.760

    The trigger was written for SQL 2005 and will not work on SQL 2000. It will take a significant amount of work to make it work on SQL 2000.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • OK, just verified by my manager that the 2000 database was auto installed from previous software that we have. It just has a SQL 2005 interface. Crap! From your comment, I can't just load 2005 standard edition over the 2000 version! Right?

    When I first started my job, I drew a 3-tier model on the board to explain the tiers of development: interface, programmin/business logic layer, and Data access and how each needed it's own dedicated resource. He looked at me and said "Wow!that's an impressive diagram". He then walked to the board and drew a big circle around all and said "you are all of these."

  • Because that instance of SQL Server is running SQL Server 2000 (80) and not SQL Server 2005 (90) or SQL Server 2008 (100).

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • rodney.williams (4/8/2009)


    OK, just verified by my manager that the 2000 database was auto installed from previous software that we have. It just has a SQL 2005 interface. Crap! From your comment, I can't just load 2005 standard edition over the 2000 version! Right?

    I've never tried upgrading MSDE to SQL 2005. In theory, it should work. I'd suggest test it out before you try on the production box, though I have no idea where one would find an install of MSDE these days.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Update: We have moved to SQL Server 2008. should I be saying "Yeah!" or "Oh crap".

    Also, your trigger is so generic, how can I make it a global trigger? Meaning all tables will use the same trigger. I suppose there would be some type of table that would hold those tables to which the trigger would be attached.

    Thanks

  • AFAIK, there's nothing like a global trigger.

    [font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
    Proactive Performance Solutions, Inc.
    [/font]
    [font="Verdana"] "Performance is our middle name."[/font]

  • rodney.williams (4/15/2009)


    Also, your trigger is so generic, how can I make it a global trigger?

    My trigger's not generic at all. It's got explicit references to the table and the columns in that table.

    As Barry said, SQL doesn't have global triggers. Every attempt I've seen to create a generic trigger that can be added to any table without modification has proved to be a performance nightmare.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 8 posts - 31 through 37 (of 37 total)

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