There's a secret to reading code. 🙂
Or rather, do it only once. Code is called code for a reason. Even the best written code is not written for readability by humans. It's written to be efficient for the computer. So despite all the code-writing best practices (linear flow wherever possible, preflight check patterning, good variable names, constants instead of magic numbers, etc. ad nauseum) code is still at best a (very) foreign language, one you will never be fluent in because there are as many "dialects" as there are developers.
Which is why at our company we specify that wherever possible code requires 70% comments to 30% code. Of course those comments should be "why" not "how" comments, and it does take effort to maintain them and make sure code changes always have comment updates as well, but the end result is rapid comprehension because you read English, not code.
Our company policy is to read the comments first, then quickly see if the code makes sense and matches the comments. If the code writer followed commenting best-practice it will. And having annotated code means having understandable code--without the need for analyzing the code. Much faster!
Of course most developers HATE comments with a passion. They hold that well-written code doesn't need them, that well written code is self-documenting. Comments make the code too long and verbose, you can't see the code for the blasted comments. And 70% comments to 30% code???? Are you joking?
Visual Studio supports code folding and code hiding. There's this nifty little extension called Remarker that lets you change comment size and color based on the type of comment. Comment headers can be normal size while comment bodies can be in a smaller font. You can then hide the comments by folding them away giving you the best of both worlds.
SSMS is a little less flexible but since SQL is so antiquated anyway it pays to keep stored procedures simple. Even so anything of any complexity should still follow the 70% comment rule. Unless it's just a simple SELECT of course. But even then you should explain WHY the stored procedure exists.
Follow comment discipline religiously and you'll find that at least in-house code doesn't have to be read--without a cheat sheet, at least! Even your own code will mystify you six-months later. Oh, and "well written code is self-documenting"? It's a LIE.