I'm not convinced that trigger are the correct solution or that the problem shouldn't be solved another way (like a a view you mentioned). But, if you are doing some leaning, here is a update trigger sample: -- SetupCREATE TABLE dbo.River_Assessments (ID INT, Listing_Category INT)CREATE TABLE dbo.River_Segments (ComID INT, Max_Pollutant INT)INSERT dbo.River_Assessments (ID , Listing_Category)VALUES (1, 1), (2, 1), (3, 1), (4, 1), (5, 1) INSERT dbo.River_Segments (ComID , Max_Pollutant)VALUES (1, 1), (2, 1), (3, 1), (4, 1), (5, 1) GO-- Create Trigger CREATE TRIGGER dbo.River_Assessments_Update ON dbo.River_Assessments AFTER UPDATEASBEGIN MERGE dbo.River_Segments AS Target USING Inserted AS Source ON Source.ID = Target.ComID WHEN MATCHED THEN UPDATE SET Target.Max_Pollutant = Source.Listing_Category;END -- Check starting pointSELECT * FROM dbo.River_AssessmentsSELECT * FROM dbo.River_Segments--Change dataUPDATE dbo.River_AssessmentsSET Listing_Category = 5WHERE ID IN (2, 4)-- Verify resultsSELECT * FROM dbo.River_AssessmentsSELECT * FROM dbo.River_Segments-- CleanupDROP TRIGGER dbo.River_Assessments_UpdateDROP TABLE dbo.River_AssessmentsDROP TABLE dbo.River_Segments