This is part 2 of my log-shipping journey, if you missed part 1, you can find it here.
I collected all of the file names I need, but you will notice I left the dates off. When my files are moved from one domain to another, their created dates are being changed. I needed the real dates for the correct restore order and to match the backups to the logs. If I were a Dark Knight Powershell master, I am sure I would have figured out how to do it. Every time I started to get close, I would would have a production issue or another distraction that needed my time. In the end I landed in my happy place, so we are fixing the dates in the database!
How do I get the right date for a file when the created date is being changed after it has moved? I was super lucky that the date is being stored in the filename too! (Huge thank you to Ola for his awesome database maintenance solution.)
An example of my filename is this:
This is how I dissect the filename to get the date and time from it:
UPDATE [DBAStuff].[dbo].[LogshippingFile] SET CreatedDate = CAST(Substring(FileName, (LEN(FileName)-18),8) +' '+ (Substring(FileName, (LEN(FileName)-9),2)+ ':' + Substring(FileName, (LEN(FileName)-7),2) + ':' + Substring(FileName, (LEN(FileName)-5),2)) AS DATETIME) WHERE CreatedDate IS NULL
My filenames are different lengths which means the the dates won’t always be in the same place, instead I go to the end of the string and count backwards because my dates are always consistent. Then I add all the parts back together to get my datetime and update it into my table.
Are we done yet? Nope, there is more.
The song for this post is Toad the Wet Sprockets’ Starting Now