Knowledge sharing

Question

Post reply

Knowledge sharing

Viewing 4 posts - 31 through 33 (of 33 total)

You must be logged in to reply to this topic. Login to reply

Jeff Moden SSC Guru Points: 1000539 More actions · Answer 1

David Burrows (11/27/2008)

And Jeff makes a good point too. Not enough of you guys get credit for posting knowledge...

Hear, hear. 🙂

But I think we all owe thanks to folks like Jeff and Steve...

Ditto 😀

..... and don't forget ....

All hail Jeff, the SQL God :w00t:

Dang, David... heh... Thanks, ol' friend!

I've gotta disagree, though... if I were a "SQL god", I'd never make mistrakes. 😛

--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.
"Change is inevitable... change for the better is not".

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)
Intro to Tally Tables and Functions

Jeff Moden SSC Guru Points: 1000539 More actions · Answer 2

Mannie, thanks for posting the article... your points are well taken and the appearance of the article is actually very timely for me. It gave me a chance to vent a little about a recent troublesome subject as well as a reminder that we all started out the same way.

--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.
"Change is inevitable... change for the better is not".

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)
Intro to Tally Tables and Functions

Tim Mitchell SSCoach Points: 15671 More actions · Answer 3

Good article, and well articulated. On behalf of those of us who have been around a while, thanks for the kind words.

I'm sure that most if not all of us veterans could tell stories about the SQL server community, and this site in particular, as being a big help to us over the years. I found SSC after inheriting a single SQL Server installation and as I accumulated more of these instances to manage, I was able to call on this group for polite and professional advice many times. I've learned a thing or two since, and try to answer as many questions as I can - though I often stand in awe at many of the other experts here.

Not that I'm bashing other forums or other database technologies, but SSC has always seemed like a cut above other forum sites. I've participated in other SQL Server forums where many of the veterans put themselves on a pedistal, and will respond unprofessionally toward those who are inexperienced but willing to learn. And good luck finding helpful forums for some of the other database vendors. I've got a couple of Big O installations that I manage, and I've not had luck finding any forums that are anywhere nearly as useful as what we have here.

Tim Mitchell, Microsoft Data Platform MVP
Data Warehouse and ETL Consultant
TimMitchell.net | @Tim_Mitchell | Tyleris.com
ETL Best Practices

Ronald Cartmale Ten Centuries Points: 1010 More actions · Answer 4

I totally agree with Manie Verster and his article Knowledge Sharing. I have found sites like SQL ServerCentral invaluable and have scoured the many articles that have been posted here and at other sites.

I started programming in SQL some ten years ago and when I joined my current company I made the assumption that the developers all knew more far more than myself, but I soon realised from the headless chicken routines and sleepless nights that in fact they knew nothing apart from SELECT * etc.

Of course, a little knowledge is dangerous and buzz words would creep into our daily lives like indexes, triggers and colleagues started to use these in the belief that they were doing it right. It was only after one disastrous deployment that never got off the ground and the subsequent witch hunt to find the cause of the failure, that I was galvanised into really getting to grips with the SQL innards.

I was fed up with having little knowledge, the long hours and sleepless nights and through various forums I was soon able to trace the cause of many SQL / Server problems and to start advising colleagues on best SQL polices.

I spent hours trawling through help forums which I found many many times more helpful than the MSDN help pages which say a lot but tell you nothing, and which if you are not careful can be lead you a merry dance following link after link until you get so lost you give up.

Like Manie, I am a slow learner when it comes to written text, but I learn quickly from diagrams and worked examples something MSDN really lacks, but once I have learnt it is there to stay.

Long live the forums and a big thank you to all who have contributed over the years.