Yes its a Store proc which gets called remotely and the restore happens through network. Now if I have to add a another step or another few lines in that Store proc. I need to go through SDLC(Dev & Engg) and which is going to take a lot of time.
Instead I would like to design a job on the target server which checks the msdb..RestoreHistory . If I have the database with today's time stamp, then shoot and email saying Publish is complete. Out database publish happens only once a day.
Not sure how to tweak the column "Restore_Date" according to my requirement which is today's Time stamp.
That's what I'm saying... just create an SQL Server Job (a "Maintenance Task" would do) to call the proc and send an email with whether or not the proc ran correctly or not.
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