DECLARE @sql varchar(max)
SET @sql = 'Update '+ @baseTable +' set Quantity = s.Quantity
from ' + @baseTable +' p , '+ @stageTbl +' s
where p.TimeKey = s.TimeKey and p.AccountId = s.AccountId and p.StockId=s.StockId'
Just to emphasize what John Mitchell posted above...
This is actually some of the most dangerous code in the whole world because it concatenates user input. Please do a search on SQL Injection both in Books Online and on the web.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs