Please contact us at editor@sql-server-performance.com for more details.
Write for Us to Make Some Money
Write for Us to Make Some Money, we pay from $25-$200 per original 1,500+ word articles on SQL Server. In order to get paid for your article, it must meet all the below criteria:
# The article must be exclusive to SQL-Server-Performance.Com
# You must give SQL-Server-Performance.Com unlimited rights to publish the article indefinitely.
# The article must be original and not duplicate existing content available on the Net or on other media.
# The article must be at least 1,500 words long, and include any necessary illustrations or code examples. Book reviews need to be at least 500 words.
# The article must be well-written using proper English spelling and grammar. The better the quality of the writing, the more I will pay.
You must contact SQL-Server-Performance.Com before you submit the article, telling us about the article. Once you get an initial OK, we will then take a look at the article. If it meets our needs (which is not guaranteed), we will then offer you an amount from $25 to $200 for the article, based on what we think the article is worth to our readers. If you agree to this, then we will publish your article and make payment to you. The amount we will offer depends on how much rewriting we feel the article needs before it is published. Payment will generally be made via PayPal.com.
If you don’t meet all of the above requirements, then we may still publish your article, if you wish, but for no payment.
What Types of Tips, Reviews, and Articles Are We Looking For?
In general, we are looking for tips, reviews, and articles on how to get the most out of Microsoft SQL Server. We are not looking for rehashes of SQL Server Books online. We prefer content that addresses the real day-to-day needs of anyone who uses SQL Server as part of their job.
Article Guidelines
Your article ideally should include the following:
* Should show our visitors how to do something useful, or how to do something better, or how to be more productive.
* Be tutorial and how-to in nature, hand-holding visitors through complicated steps. If appropriate, provide step-by-step instructions.
* Provide practical, real-world information, with minimal theory.
* Include lots of examples, including code (if appropriate), tables, figures, screen shots.
* Code examples should not exceed 50 percent of the length of the article.
* Include lots of practical advice based on your own real-life experiences.
* Explain the “why” along with the “how-to” (very important).
Tip Guidelines
Your tips ideally should include the following:
* Should not repeat a tip that is already on the website. Before writing the tip, search the website to ensure that it has not been discussed before.
* In some cases, if a current tip does exist, and you think it can be substantially improved, then that is OK, as long as you have added substantial new content.
* New tips should fit into one of the tip categories listed on the home page of the website. If it does not fit into any of these categories, and you think it is important, contact me to discuss it. Also, be sure to tell me what category you think your tip fits into.
* Should show our visitors how to do something useful, or how to do something better, or how to be more productive.
* Be tutorial and how-to in nature, If appropriate, provide step-by-step instructions.
* Provide practical, real-world information, with minimal theory.
* If appropriate, includes code examples.
* Include lots of practical advice based on your own real-life experiences.
* Explain the “why” along with the “how-to” (very important).
* Be sure you review the current tips on the website, and use them as a model when writing your own tips.
More information here.
skip to main |
skip to sidebar
