4

It seems sqlblog.com is now sqlblog.org 1.. One effect of this is to break outgoing links from dba.se.

In the past, I've tried to be a good netizen 3,4,5,6 and edit posts with dead links to an appropriate new home or archive copy (god bless the wayback machine - RIP MS Connect). Sadly in this case, I'm not even able to submit the suggested edit (.com -> .org) unless I spam in filler characters to meet the minimum edit length.

In general - these outgoing links were helpful at the time and still can lead to useful additional relevant information. Is there a general solution for finding and repairing damaged links across the network?

I have in mind the Community-bot going about and hoovering up http -> https redirects for SE, but I'm not aware of any community-supported solution for arbitrary pattern updates.

...although...

...as I dig into my own revision history for examples... I did notice this interesting edit history - so... is that a generally supported solution? If so, how does the general (low-rep) community make suggestions to it?


1. as of like like... well... earlier this year way to stay up to date, self...🙄

N.B. this is not an isolated problem: https://blogs.msdn.microsoft.com/extended_events/2010/03/17/extended-blogs-now-cross-posting-to-sqlblog-com/

  • 1
    The revision history in your penultimate link shows a sqlblog.com link having been replaced with a Wayback Machine link. I took the original link, replaced .com with .org and tried opening it like that, and what do you think? It didn't work. So fixing all those links might not be as easy as just replacing the TLD. – Andriy M Nov 14 '18 at 9:28
  • 4
    Just to clarify something, sqlblog.com did not become sqlblog.org. sqlblog.org is actually just Aaron Bertrand's blog. See Same old content, brand new home. Which is why the example from @AndriyM doesn't work (that's Paul White's post, and thus was not migrated to Aaron's blog at sqlblog.org). – jadarnel27 Nov 14 '18 at 15:48
6

It is always awkward when links break (though as of today sqlblog.com is back up).

Aaron has relocated his content from sqlblog.com to sqlblog.org.

Nick Craver offered to help Aaron automate the process of updating links.

tweet

I imagine the Community updates noted in the question came out of that process.

I have relocated my own sqlblog.com content to https://sqlkiwi.blogspot.com.

General advice

If you come across posts with broken links and are able to fix them, please do so. If there is really nothing else that could be improved in the post and you come up against the minimum edit length restriction, flag the post for a moderator. We are happy to take care of such things, but please include all the information we need to make the edit in your custom flag description. Or post in The Heap to get someone with full edit privileges to make that change for you.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .