ScottD's Musings

Here are some interesting “finds” from the blogging world over the past week or so (I’m offloading all my saved Favorites here!)

It’s 11:40pm and I’m currently reviewing email received throughout the day, awaiting the 2-3 inches of snow expected in the Dallas area (yes not much, but hey, the whole metroplex shuts down at the first hint of winter weather, which usually melts by 10:30 the next morning).

One of Telligent's other Scott's, Scott Watermasysk, recently blogged a post that should help answer quesions surrounding future updates to his .Text engine.  In addition he provides insight to the product's evolution into CommunityServer.

As blogged earlier, Microsoft's Patterns & Architecture Guidance group's latest code offering, Enterprise Library, was released today.

[From Mark Fussell!  THANKS MARK!]

Upon the release of SQLServer 7, our DBA warned us about naming our stored procedures starting with “sp_”, that it actually decreases performance.   I thought he was crazy.  “What is he talking about?  How could that possibly be true?  The name of a stored procedure name decrease performance?  Whatever!”  I jotted a note to research it when I got a second, just to prove him wrong, but never followed through with it.  The good news (for our clients) is that I never used the “sp_” prefix, however.

Being a middle-tier guy, as well as being anal about standards & conventions, I really wanted to expand on my standards documents authored for clients, and write a verbose standards document to share with the community.  Since then, I’ve realized a few things.  First, a good friend of mine convinced me that quick, bullet-list, to-the-point documents are used more readily than verbose 100+ page guidelines.  So far in my experience with clients & consultants, I've found that to be the case.  Second, many people have put together some great work in this area!  Check out the work that these people/teams have put together on this topic:

[From Lance Hunt]