Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

Update in all table Expand / Collapse
Posted Wednesday, October 24, 2012 6:01 AM



Group: General Forum Members
Last Login: 2 days ago @ 4:58 AM
Points: 2,087, Visits: 2,654
I have written an update statement which is updating some fields like this--

update L
set L.UpdateBy = E.UserID,
L.CreatedByID = E.UserID
from EmployeeProfile E
inner join LocationMaster L on E.EmployeeID=L.UpdateBy

As it will only updating in LocationMaster table.
I want to update all the tables that has columns(UpdateBy,CreatedByID).
Is it possible?

To get quick answer follow this link:
Post #1376424
Posted Wednesday, October 24, 2012 6:14 AM



Group: General Forum Members
Last Login: Today @ 2:07 PM
Points: 13,784, Visits: 35,423
you could build the queries you want to execute for all tables meeting your criteria.

if the table has a value in the UpdateBy column, are you trying to set the CreatedByID tot eh same value?
what is the purpose of joining to the Employee table if the data is already in the target table anyway? if the data is blank in LocationMaster, your update will leave those rows null still.

Anyway, as far as building the query goes,
my example below below builds the same SQL statement you demoed for every table that has both a UpdateBy column and a CreatedByID column.
is that what you want?
it's a little wierd to want to blindly update like that...since the data is already there!

update L
set L.UpdateBy = E.UserID,
L.CreatedByID = E.UserID
from EmployeeProfile E
inner join ' + OBJECT_NAME(T1.object_id) + ' L on E.EmployeeID=L.UpdateBy
' AS cmd
FROM sys.columns T1
INNER JOIN sys.columns T2
ON T1.object_id = T2.object_id
WHERE = 'UpdateBy'
AND = 'CreatedByID'

is this what you are really trying to do?
update LocationMaster
set UpdateBy = CreatedByID
--AND UpdateBy IS NULL --?? only where it's currently blank/null?


--There is no spoon, and there's no default ORDER BY in sql server either.
Actually, Common Sense is so rare, it should be considered a Superpower. --my son
Post #1376429
Posted Wednesday, October 24, 2012 6:28 AM



Group: General Forum Members
Last Login: Tuesday, September 29, 2015 3:15 AM
Points: 115, Visits: 149
the MERGE statement might help you there but I would create separate update statements and run as a single transaction. Also use nested if statements so that if one update fails everything gets rolled back.

make sense?

Post #1376434
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse