SQL Server Performance

Looking for Software Reviewers

Discussion in 'Forum Announcements' started by bradmcgehee, Feb 3, 2006.

  1. bradmcgehee New Member

    With the new release of SQL Server 2005, a lot of companies have upgraded their SQL Server-related software, so much, that we can't keep up writing all the reviews.

    So we are looking for some people who might want to help out writing some reviews for us.

    If you are interested, we will pay up to $100 USD for each review, and also, depending on the software company, you may get a free license to the software you review.

    If you are interested, first read our writer's guidelines at:

    http://www.sql-server-performance.com/write_for_us.asp

    Then, read some of the current reviews at:

    http://www.sql-server-performance.com/spotlights.asp

    In addition, below, I have posted some very specific review guidelines below.

    Once you have done all of this, and you are interested in trying to write a review, please contact Brad M. McGehee at:

    webmaster@sql-server-performance.com

    for more information.




    Software Spotlight Guidelines:

    1,500+ Words
    4-8 Screen Shots

    Try out the software and explore all the available features. Read the documentation. Do the research.

    You're ready to write the review when you can answer these questions: What does the product promise? How well does it deliver on this promise? Is the product a good value? For whom? (For us, this will always be a DBA or SQL Server developer.)

    At-a-Glance Information: Product name, version evaluated, full company name, price, company URL.

    Use the company's capitalization, punctuation, and spacing for product titles.
    Introduction (200-400+ Words):

    What problem is this product going to solve? In the lead paragraph, state the problem to be solved and why the product is a possible solution to this problem. The problem must relate specifically to a DBA or SQL Server developer. How well does this product solve the problem? End the lead paragraph with a one-sentence summary of your opinion of the product but without giving any details of that opinion (you'll give them later in the review).

    Additional paragraphs in the introduction can provide brief background information, a summary of key features and benefits, the product's advertising claims, or other pertinent information. (Key features and benefits are only those that are worth mentioning briefly in the introduction because they are exceptional, poor, or unique and interesting.)


    Evaluation (900-1200+ Words):

    Describe what the program does (what it promises) and explain how it works. Summarize its operations and features as it relates to the promise and the problem to be solved. If you want to provide a full feature list, do so as a chart.
    Do not provide a step-by-step description of the installation process. You may summarize the process, but be specific only if there's something significantly wrong with either the process or the vendors' instructions.

    Next, describe in detail what you like about the program, and why. Describe anything outstanding or unique about the program. Then describe what you don't like about the program, and why, if appropriate. Describe anything that doesn't work properly or anything you consider important that is missing.

    Avoid repeating the program's name frequently.

    Screen shots: One screen shot (usually the first) must show what the program looks like when it first loads – that is, the full interface. Other screen shots always show the program in action: menus, procedures, errors, etc.


    Conclusion (100-200+ Words):

    This is your summary paragraph. What is your reaction to the program? How well did it deliver on its promise? What is its value to a DBA or SQL Server developer? Summarize your overall impression of the software and provide a strong conclusion. In your recommendation, do not use a rating system. Simply make your recommendation in the summary, and don't forget to say why you are making that recommendation.

    Always include some statement, similar (but not identical) to the following: "Is this product for you? The only way to really find out is to download the trial version and try it for yourself." (This is the call to action.)


    -----------------------------
    Brad M. McGehee, MVP
    Webmaster
    SQL-Server-Performance.Com

Share This Page