Tail log backup WITH CONTINUE_AFTER_ERROR works only if the database goes offline in case during the start up of the database is fail to come online due to some reasons or damaged due to some reason, in case if we did purpose fully then that will not work (i,e the database didnt have any issues at all)
True, now I took the time to manually "corrupt" one of my test databases (not only take it offline) and I was able to do a tail-log backup WITH CONTINUE_AFTER_ERROR and also to restore the database to that transaction log backup.
Definitely I learned something today. Good question!
Thank you, raul and twin;
your script and the twin's extended explanation is really really really ... really extraordinary information in this section.
(had a vague idea..... after reading the question and then the raul's script- I started to think like this "server putting database offline" and/or "putting database manually offline"..... and then I jumped "well offline is an offline" ended with a absolute wrong conclusion, thank you twin for really good insight on this. this makes so much sense to me now...)
To author: very interesting question, thank you for the post.
The first and the hardest SQL statement I have wrote- "select * from customers" - and I was happy and felt smart.