Today’s SQL Saturdays post discusses a cute little trend we have going on SQLServerCentral.com, SQL Spackle articles.
SQL Spackle articles are short and simple articles meant to spackle, or patch, existing knowledge gaps. While Microsoft’s Books Online covers a lot of information, it also leaves out information that DBAs and Developers have to discover on their own. Plenty of articles have been written by very knowledgeable people on the big stuff such as backups, restores, major code How-Tos. But several members of the SSC community noticed that the small stuff, which is needed just as badly, is rarely covered.
Hence the birth of the SQL Spackle article. At the head of each little article is the following disclaimer:
“SQL Spackle” is a collection of short articles written based on multiple requests for similar code. These short articles are NOT meant to be complete solutions. Rather, they are meant to “fill in the cracks”.
–Phil McCracken
SQL Spackle fulfills a need rarely recognized by the technical community, those useful little code bits that everyone can share, use, and save in their own personal libraries to port from job to job. The intent is to reach everyone regardless of their experience and knowledge level. It seems to be working out fairly well, too.
So if you or someone you know is hitting a wall or looking for that little bit of extra info not included in the usual sources, check out SSC’s SQL Spackle library. There’s some interesting stuff, including one article of mine that just got published two days ago, Schema-Owned Tables and Generated DROP Scripts. (Because I keep running into this problem myself, and remembering the solution is easier for me if I actually write about and share it.)
Do you have ideas for more SQL Spackle articles? SSC pays for both these and regular SQL Server articles. Check out their Write For Us page. Join the fun and spackle a few holes in the process. You’ll be glad you did!
