June 24, 2015 at 10:32 pm
Comments posted to this topic are about the item #SQLNewBlogger
June 25, 2015 at 3:16 am
Steve knows that I signed up right away and even managed to get 5 blogs[/url] done in April. Since that time, my output has dropped off a bit due to other challenges in my work and personal life. I can say that it was fun, and quite a challenge to write regularly. Steve pushing (and some of the tips from his blog) certainly helped.
Two guys were doing weekly digests of the results posted to the hashtag:
Andy Levy[/url] (there are links at the bottom to digests after week 1)
I think Andy said his automated digest would keep running, but I believe Aaron's was a manual round up so may not have everything posted since April. Still these will give you a good summary of what's been done.
I encourage Steve's suggestion to keep this going and will do my best to continue to contribute!
Perhaps Andy or Aaron will see this and refresh their digests.
And by all means get a Twitter account if you haven't already so you can send out your blog links. I rounded up most of the participants early (encouraging the group to follow each other) so we could all see what each other was up to in their blogs. So I encourage you to do the same. I still check the hashtag regularly to get latest updates.
Happy and productive blogging to you all!
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St
June 25, 2015 at 3:17 am
Excellent article , easy to understand ( nice for the readers for which the English language is not the mother tongue as for me ).
Just a surely stupid question ( I hope that I will not be vexating anybody ) : for bloggers who are not sure to write in a good and fully understandable English language , is it possible that someone can reread the text and show where errors or difficulty understandable expressions are appearing ?
June 25, 2015 at 3:25 am
patricklambin (6/25/2015)
Excellent article , easy to understand ( nice for the readers for which the English language is not the mother tongue as for me ).Just a surely stupid question ( I hope that I will not be vexating anybody ) : for bloggers who are not sure to write in a good and fully understandable English language , is it possible that someone can reread the text and show where errors or difficulty understandable expressions are appearing ?
Note the advice in my prior post here about the mini-Twitter community of #SQLNewBloggers. One of the members in that community pinged me during the April competition to ask me if I'd review one of his blogs and I did. I can't promise to always be available to do so but with a community watching, surely someone would be happy to step up.
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St
June 25, 2015 at 3:58 am
dwain.c (6/25/2015)
patricklambin (6/25/2015)
Excellent article , easy to understand ( nice for the readers for which the English language is not the mother tongue as for me ).Just a surely stupid question ( I hope that I will not be vexating anybody ) : for bloggers who are not sure to write in a good and fully understandable English language , is it possible that someone can reread the text and show where errors or difficulty understandable expressions are appearing ?
Note the advice in my prior post here about the mini-Twitter community of #SQLNewBloggers. One of the members in that community pinged me during the April competition to ask me if I'd review one of his blogs and I did. I can't promise to always be available to do so but with a community watching, surely someone would be happy to step up.
Thanks for your quick ( 15 minutes you are Speedy Gonzales ) and reassuring reply ( I am not sure that Bing Translator is a minutes good product and I am searching my Harrap's dictionary since an hour unsuccessfully )
June 25, 2015 at 3:59 am
I'd certainly be happy to help check English for people. It will also encourage me to get reading blogs. I'd not even remotely consider myself able to check the technical side of things though.
How to post a question to get the most help http://www.sqlservercentral.com/articles/Best+Practices/61537
June 25, 2015 at 6:14 am
I'd blog more, but 95% of my coding is for my current job and getting anything even remotely related to the work I do released for any sort of publication is a legal/bureaucratic nightmare. The only database/programming topics I can legally blog on are non-Microsoft, non-industry, very basic vanilla issues.
:crying:
June 25, 2015 at 7:15 am
One easy source of topics is SQL 2016. Lots of new features. Explore them. What questions do you have as you start on each? Write them down and work out the answers. That way it's industry related but not work related.
June 25, 2015 at 7:21 am
We've started putting lists together of SQL 2016 related content, so feel free to try things out and write about it: http://www.sqlservercentral.com/articles/SQL+Server+2016/127518/
June 25, 2015 at 7:25 am
When I was still blogging, it was very rare that something I wrote was related in any way to what I was working on. More often they were inspired by common questions here.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 25, 2015 at 7:37 am
One easy source of topics is SQL 2016. Lots of new features. Explore them. What questions do you have as you start on each? Write them down and work out the answers. That way it's industry related but not work related.
No it's worse than that. If it's a piece of software I use at the job, I have to get clearance to post/write/speak about it. Since 95% of my day job is Microsoft based, I can only blog/write/speak on non-Microsoft software, unless I jump through a bunch of hoops and get approval.
(Note, all of my side work is non-Microsoft, usually open source. Company doesn't care about that since they are very dismissive of that "Hippy Free Cr*p")
June 25, 2015 at 11:23 am
Rod at work (6/25/2015)
I like the challenge, Steve. Even Accidental DBA's like myself? I'll try; see how it goes.
Good luck and keep following the #sqlnewblogger on Twitter.
June 27, 2015 at 8:25 am
I am more of an accidental DBA and the data sets I manage are actually incredibly small however they are highly relational and particularly complicated as such my blog is more a generalists notepad with tinges of SQL and databases.
I do find it is absolutely great though for storing snippets of code that I use infrequently. It is also absolutely brilliant for explaining to colleagues requests for things that they themselves carry out very infrequently. I sometimes have to instruct others to carry out procedures because I do not have the requisite permissions but I am aware that those that are carrying out the work on my behalf are not familiar with what to do. A well written blog post on what I am requiring can be invaluable in these circumstances.
And of course by having a dynamic reference rather than an instruction in an e-mail - when (and it is often) I give either a vague or downright incorrect instruction I can go back and correct it rather than chasing wrong e-mails which I find very frustrating.
It does mean some of my posts are very specific and brief.
I do believe blogs are far far better than CVs for indicating someones knowledge
June 28, 2015 at 5:18 am
I have a few blogs myself, but nothing on the tech side of things.
I've thought about writing something dedicated to what I do for living now, but as others mentioned, I'm also the accidental DBA, ETL Developer, Report Developer and so on.
Although that doesn't really prevent me from writing about it. The problem is the landscape is flooded with loads of good blog articles about potentially every subject surrounding SQL Server. I would go as far to say that a good majority of them are covered officially and unofficially from a handful of sites and organizations pushing a product/service.
So, it makes it extremely hard to find anything to write about that is offering anything of value.
Viewing 15 posts - 1 through 15 (of 18 total)
You must be logged in to reply to this topic. Login to reply