quote:

---

Originally posted by gbritton

assuming a sensible naming convention, could use the undocumented sp_foreacthtable

---

USE [Home Care]
GO
/****** Object:  Trigger [dbo].[Patient_Name_Updated]    Script Date: 12/16/2014 9:01:26 AM ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO

ALTER TRIGGER [dbo].[Patient_Name_Updated] 
   ON  [dbo].[Patient] 
   AFTER UPDATE

AS 
BEGIN
SET NOCOUNT ON;

    If (UPDATE (Firstname))
    BEGIN
	    UPDATE QANursingForms SET PatientName = Patient.Compined
		FROM Patient
		INNER JOIN QANursingForms ON QANursingForms.ClientID = Patient.ClientID AND QANursingForms.MRNum = Patient.MRNum
	END

	If (UPDATE (Lastname))
    BEGIN
	    UPDATE QANursingForms SET PatientName = Patient.Compined
		FROM Patient
		INNER JOIN QANursingForms ON QANursingForms.ClientID = Patient.ClientID AND QANursingForms.MRNum = Patient.MRNum
	END
END

quote:

---

Originally posted by gbritton

Well... yes but you said 50 tables. A trigger updating 50 other tables is not a reasonable permanent solution.

---

quote:

---

Originally posted by tkizer

You can cascade updates if the columns are in a foreign key constraint, though I wouldn't expect patientname to be in all of those tables since the name can change. I would think an identity column would be used instead, which would never get updated. I would not recommend sp_foreachtable for this nor a trigger.

It seems to me that you have a design issue that needs to be fixed before proceeding.

---