Balancing SQL Server 2005 and 2000 Coverage

With the release of major new products such as SQL Server 2005, it's easy for magazines and authors to fall into the trap of writing only about all the new toys. But many readers will be using SQL Server 2000 for months, if not years. Some of you probably want to see mostly SQL Server 2000 coverage, some of you want mostly 2005 coverage, and many of you will want a healthy mix, although you'll probably disagree what the mix should be. In addition, you probably want a healthy mix of coverage of BI, developer, and DBA topics, depending on your job's focus. It's a good thing I get to write 50 of these columns per year because I sure have a lot of important topics to cover!

SQL Server Magazine editors and columnists have been chatting about this topic. We've learned our lessons from past upgrade cycles and certainly don't want to abandon folks who rely on earlier versions of the products we cover. But we do want to stay relevant and fresh. We've done all sorts of polls to gauge what you want--and don't want--to be reading about. But it's been a while since I posed an open question directly to SQL Server Magazine UPDATE readers regarding my commentary.

I thought about doing a poll with fixed questions and answers, but I decided against it. I'd never think of the right leading, probing questions to fully capture all the interesting ideas and comments that I hope you'll have to share. So consider this an open request. How am I doing? What do you want to be reading about in my UPDATE commentary section? Tell me. I can't promise to satisfy everyone, but I will promise to read each response and do my best to integrate the feedback into my commentary and analysis for 2006.

Note that I write this editorial piece but not the rest of the UPDATE content, so please segment your thoughts and opinions based on whether it's directly related to my editorial. That way I can make sure your comments are routed to the folks who can act on them. But regardless, send me your thoughts today at [email protected] and let your voice be heard!

Hide comments


  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.