Are you looking for opportunities to show off your elite writing skills and consumate SQL Server knowledge? Want a chance to build up the resume a bit? Are you like me and you have a hard time thinking of ideas to write about? I’ve got a solution for you. There’s a new forum over on SQL Server Central that is all about requests for articles. It’s mostly small stuff, easy one-page articles, a bit more than a blog post but a bit less than a full blown multi-page drill down. Also, if you have ideas for articles that you’d like to see someone write up, you can post them there. You should read the rules about the forum, which aren’t complicated, and then dive in.
I’d really like to publish your article in SQL Server Standard. All I need from you is an abstract, a description of what the article will be. I’ve posted this before, but I’ve never provided examples. So, to get people started, here are a few examples of articles that have been accepted and will be published (shortly I hope).
Here’s a great example from Andy Leonard. It includes a great amount of detail, more than I need to make my decision, but with this much detail, the decision is much easier because I know exactly what this article is likely to look like:
I’m interested in writing an article on SSIS for SQL Server Standard. I’d like to cover ways packages can exchange information at run-time. There are a couple obscure ways parent-child packages interact that make for some interesting design opportunities and architectures – especially when combined. For example, most SSIS developers realize Events “bubble” up through EventHandlers; so that if a Control Flow contains a Sequence Container which contains an Execute SQL Task, an error generated at the Execute SQL Task will raise the tasks’ OnError EventHandler, then the Sequence Container’s OnError EventHandler, and finally the OnError EventHandler of the package. What’s not so well know is: If a package calls another package via the Execute Package Task, the calling package is said to be the parent (or master) package; the called package is the child. In this scenario, events raised in the child at the package level will bubble to the parent package.The second obscure behavior is variables in the parent package are inherited in the child package. The cool thing is: they’re inherited ByRef – unlike parent package configurations, which pass variable values ByVal from parent to child. ByVal is one-way communication; ByRef is bi-directional, which means I can make a change to a variable in the child package and that change will persist in the parent after the child package has completed executing.
It is common knowledge that Application Programmers and DBAs don’t get along in many cases, and the root of this is that the two technologies are fundamentally different. It is also common knowledge that many Application Programmers write SQL as part of their job. However, often their familiarity with loop-based programming is their undoing, taking them down strange SQL paths that produce bad SQL code and make their relationship with the DBAs even worse. This article will show how difficult the transition is, even if it doesn’t seem to be at first, and how you have to adjust your thinking in order to successfully program in T-SQL.
In this article, I will give you a practical overview of how to design effective partitioning schemes. I will cover good partitioning design, the differences between aligned and non-aligned indexes, and some examples of when to use each. I’ll also discuss some issues to be aware of when designing partitioning schemes, including performance, replication, and sliding-window considerations.
Andy Warren in the latest PASS Connector has posted an update on where we’re at with the SQL Server Standard. I’m so happy that Andy has been keeping this out in front of people. It provides some impetus to get the work done. Except for the authors thanks (and they’re receiving $500, so they should say thank you), there’s very little feedback on the Standard to show whether or not people are interested, if the goals and ideas are worthy… In other words, you guys need to let us know what you think about the thing.
Two more articles are in the hopper to be published. Another has gone into copy edit. We’re technical editing two others. That’s five more, so you guys can expect to see another ten weeks worth of SQL Server Standard. But after that…
Don’t you want $500? Just submit an abstract and your writing history to email@example.com. We’ll get you started.