Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««56789»»

Writing Expand / Collapse
Author
Message
Posted Wednesday, May 14, 2008 9:02 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, August 1, 2014 8:17 AM
Points: 12, Visits: 62
Imagine when someone is looking for a solution for a coding problem , its a happy moment when you find what you look for online , more writing means more happy moments for others who are looking for information .
Post #500588
Posted Thursday, May 15, 2008 3:33 PM


Keeper of the Duck

Keeper of the Duck

Group: Moderators
Last Login: Monday, August 18, 2014 8:24 AM
Points: 6,634, Visits: 1,871
I know I'm very late to the conversation, but a few things...

People learn in different ways. Just because there's an article out there describing RAID configurations doesn't mean Joe SysAdmin is going to get it because of that article. Your article, which may come at it in a slightly different direction or just your choice of words, or the fact that Joe SysAdmin is processing multiple articles may lead to Joe "getting it." So just because you see an article out there on something doesn't mean you have to stop from writing about it, too.

You don't have to be an expert to write. One of my first articles on the old swynk.com garnered a reply from none other than Steve Jones who offered a different perspective on the same topic. It gave me a lot of things to think about and I went ahead and amended my article with some of Steve's points because they made a lot of sense. The majority of us aren't in the Kalen Delaney or Itzik Ben-Gan stratosphere of SQL Server knowledge. We don't have to be. Which is a good thing, or I'd have never written anything...

Time is always an issue. It's why I bounce in and out of the forums and the blogs where I'm posting like a madman for a few days and then disappear for weeks at a time. I keep telling Steve I'm going to start writing again and then I get busy between work, family, and ministry. I do know that when I was writing all the time, it was easier to write (as Phil Factor indicated). I do a lot of writing now, but it's for ministry, and I know that's something I'm called to do. Here's the thing, when I was churning out SQL Server articles once or twice a month, I found writing about 15-20 minutes a day was enough to get that kind of output and more. Since I'm writing daily for ministry and since I'm doing a lot of checking, cross-referencing, researching, exegetical analysis, that kind of writing takes a lot longer. But the technical writing is finding a particular topic you have an interest in, spending probably 2-3 hours over the course of a week or two and it's out there. Which I guess incriminates me for not writing on here more. *shrug*




K. Brian Kelley, CISA, MCSE, Security+, MVP - SQL Server
Regular Columnist (Security), SQLServerCentral.com
Author of Introduction to SQL Server: Basic Skills for Any SQL Server User
| Professional Development blog | Technical Blog | LinkedIn | Twitter
Post #501679
Posted Thursday, May 15, 2008 9:35 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 3:06 PM
Points: 33,169, Visits: 15,304
Brian, we'd love to have more, and we miss your great information, but we completely understand you working on other projects.

You do what you can, and what your passion is. If it's writing somewhere else, enjoy it. If you want to try it here, let me know.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #501753
Posted Wednesday, May 21, 2008 7:06 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 9:46 AM
Points: 7,089, Visits: 6,898
Actually, the real reason why I write is because...

I can't remember stuff no mo'.

And you are ?

lol only kidding Jeff ;)

Keep think about submitting something but can't think of anything that ain't already been done

Maybe one day ......... :D

wonder if I could plagiarize Jeff's work

All hail Jeff !!!



Far away is close at hand in the images of elsewhere.

Anon.

Post #504434
Posted Wednesday, May 21, 2008 6:50 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 3:51 PM
Points: 36,959, Visits: 31,469
David Burrows (5/21/2008)
Keep think about submitting something but can't think of anything that ain't already been done


Actually.... everything I've written about is NOT new... Tally table is old hat... has been for a long time. I didn't even invent it. But there are a lot of folks out there that knew nothing of it and, it never hurts to see how other people explain the same thing.

I saw one article by a fellow recently. He wrote about a handful of (I thought) very well known undocumented stored procedures like sp_MSForEachTable. Some folks made some pretty nasty comments about writting about something so obvious. But, to those that don't know, it's no so obvious. Sure, people can search for such things, but like all such research, most folks need to know that such a thing even exists before they can do a search.

I've been following your posts for years, David... you'd write a great article even if it was on something "obvious"... you have the "knack".


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #504926
Posted Wednesday, May 21, 2008 10:12 PM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 5:09 AM
Points: 5,338, Visits: 1,385
David Burrows (5/21/2008)
Actually, the real reason why I write is because...

I can't remember stuff no mo'.

And you are ?

lol only kidding Jeff ;)

Keep think about submitting something but can't think of anything that ain't already been done

Maybe one day ......... :D

wonder if I could plagiarize Jeff's work

All hail Jeff !!!


You can submit old in a new bottle :)



Post #504972
Posted Thursday, May 22, 2008 7:00 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 2:24 PM
Points: 11,235, Visits: 12,988
Jeff Moden (5/21/2008)
David Burrows (5/21/2008)
Keep think about submitting something but can't think of anything that ain't already been done


...

I saw one article by a fellow recently. He wrote about a handful of (I thought) very well known undocumented stored procedures like sp_MSForEachTable. Some folks made some pretty nasty comments about writting about something so obvious. But, to those that don't know, it's no so obvious. Sure, people can search for such things, but like all such research, most folks need to know that such a thing even exists before they can do a search.
...


I worked with SQL Server for almost 9 years and while I had "heard" about the sp_MSForEach stored procedures I had never used them and still have not, but the article did provide some ideas on how to use them. There are also some instances where I may use sp_MSForEachTable in the near future and I would have done it by hand if not for this article on "well known" undocumented stored procedures.

As this demonstrates any article published will likely find someone who needed to know what was in it. I look at as, if I provide help to 1 person the time and effort it took to write the article is worth it. Granted I have only written 1, but I did find it quite rewarding.




Jack Corbett

Applications Developer

Don't let the good be the enemy of the best. -- Paul Fleming

Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
How to Post Performance Problems
Crosstabs and Pivots or How to turn rows into columns Part 1
Crosstabs and Pivots or How to turn rows into columns Part 2
Post #505147
Posted Thursday, May 22, 2008 7:18 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Today @ 4:11 PM
Points: 15,646, Visits: 28,027
Also, while lots of people may have one piece of knowledge or another, maybe a full set of the knowledge has never been put in one place before. I wrote up an article for Steve on how to collect data into SCOM from a TSQL query. Nothing in the article isn't available elsewhere. As a matter of fact, throughout the article I point to all the places to get the individual pieces that I was working from. However, this is the first place that all these things will be brought together in one place. It's not that I'm inventing something new or special. I'm just publishing my research so that the next guy has a slightly easier time of it.

----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #505157
Posted Thursday, May 22, 2008 7:32 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Wednesday, May 11, 2011 1:33 PM
Points: 85, Visits: 299
Grant Fritchey (5/22/2008)
Also, while lots of people may have one piece of knowledge or another, maybe a full set of the knowledge has never been put in one place before...


Following up on what Grant said, I think our Google-search dominated world, we expect to find answers to all of our questions via a simple search. Well, if the answer is fragmented on the web (which it often is), Google can help us find all the pieces. But it is still up to us to assemble them into a solution. Therefore, there is always a need for someone to put the pieces all together into a single, concise and meaningful form, so that no one else needs to repeat the process. This is how we make the greatest progress.


---------------------------
|Ted Pin >>
Post #505172
Posted Friday, May 23, 2008 8:16 PM


Keeper of the Duck

Keeper of the Duck

Group: Moderators
Last Login: Monday, August 18, 2014 8:24 AM
Points: 6,634, Visits: 1,871
Agreed. When I was writing all the time on security, my later articles started including a section called references. My point for including those links was to give folks more sources to use to better understand what I was writing about. Some times I was pulling things together from multiple sources. I knew it took me some time to do that to find a solution to a problem I was working on, and I knew I wished someone had already done it. So I wrote the article and cited the references. Because there are some out there who want the immediate solution but they are curious and want to read more.


K. Brian Kelley, CISA, MCSE, Security+, MVP - SQL Server
Regular Columnist (Security), SQLServerCentral.com
Author of Introduction to SQL Server: Basic Skills for Any SQL Server User
| Professional Development blog | Technical Blog | LinkedIn | Twitter
Post #506189
« Prev Topic | Next Topic »

Add to briefcase «««56789»»

Permissions Expand / Collapse