Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. Database
  4. T-SQL

T-SQL

Scheduled Pinned Locked Moved Database
databasequestionannouncement
4 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • W Offline
    W Offline
    Werries
    wrote on last edited by
    #1

    Hi there, Is there a way to include a value from the affected record into a AFTER UPDATE trigger? And if there is a way, can you give me an exapmle, please? Thanks, Werries

    A programmer's life is good... or is it?? Ek dink nie so nie!

    M 1 Reply Last reply
    0
    • W Werries

      Hi there, Is there a way to include a value from the affected record into a AFTER UPDATE trigger? And if there is a way, can you give me an exapmle, please? Thanks, Werries

      A programmer's life is good... or is it?? Ek dink nie so nie!

      M Offline
      M Offline
      Mike Dimmick
      wrote on last edited by
      #2

      Use the inserted or deleted pseudo-tables depending on whether you want the values after or before the update occurred. Remember that more than one record can be affected by a statement, but that the trigger only fires once, regardless of the number of records affected.

      Stability. What an interesting concept. -- Chris Maunder

      W 1 Reply Last reply
      0
      • M Mike Dimmick

        Use the inserted or deleted pseudo-tables depending on whether you want the values after or before the update occurred. Remember that more than one record can be affected by a statement, but that the trigger only fires once, regardless of the number of records affected.

        Stability. What an interesting concept. -- Chris Maunder

        W Offline
        W Offline
        Werries
        wrote on last edited by
        #3

        Thanks for your reply Chris, I appreciate it. Regards, Werries

        A programmer's life is good... or is it?? Ek dink nie so nie!

        C 1 Reply Last reply
        0
        • W Werries

          Thanks for your reply Chris, I appreciate it. Regards, Werries

          A programmer's life is good... or is it?? Ek dink nie so nie!

          C Offline
          C Offline
          Colin Angus Mackay
          wrote on last edited by
          #4

          Werries wrote:

          Chris

          Who's Chris?


          Upcoming events: * Glasgow: SQL Server 2005 - XML and XML Query Plans, Mock Objects, SQL Server Reporting Services... Never write for other people. Write for yourself, because you have a passion for it. -- Marc Clifton My website

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups