It’s time to wrap up T-SQL Tuesday for the year 2010 and I was invited to host his month’s blog party by Adam Machanic (Blog | Twitter).

What’s T-SQL Tuesday?

This monthly event is the brainchild of Adam, and you can read about the inspiration in his very first T-SQL Tuesday post. Adam Machanic , a long time SQL Server MVP came up with an excellent idea of improving community involvement around blogging where bloggers around the world post their views on a same topic chosen by the host on the 2nd Tuesday of every month. If you are interested in hosting an event like this and then send a note to Adam.

What are the rules?

1. Since this is a global event, your post should go live between 2010/12/14 00:00:00.000 GMT (2nd Tuesday) and 2010/12/15 00:00:00.000 GMT. Since those of us in the US as sometimes date challenged, that’s sometime during Dec 14, 2010 using GMT time.
2. Your blog post has to link back to the hosting blog, and the link must be anchored from the logo (found above) which must also appear at the top of the post.
3. If trackbacks won’t work properly then please leave a comment below so that your post is accounted for in the roundup.

Nice Things To Do

1. Include a reference to T-SQL Tuesday in the title of your post. (The more we bloggers advertise T-SQL Tuesday, the more we bloggers get T-SQL Tuesday readers)
2. Tweet using the hash tag #TSQL2sDay to follow links and other relevant conversations.
3. consider hosting T-SQL Tuesday yourself. If you’re interested let Adam Machanic Know. If you’ve participated in two T-SQL Tuesdays previously and you don’t let your blog go stale (blog once a month for the last six months) then he’ll put you in the rotation.

The Topic

I was giving a presentation recently and someone in the audience started to ask about why I recommended against a certain technique. Without getting into it, this person kept saying that she had to implement things her way since the “business” said they needed it done that way. However a little digging showed that the business didn’t really understand the technology. They were asking for a result, and she took them literally in how she implemented a process. A classic impedance mismatch.

I think we’ve all had situations that are similar. The business, the client, the customer, is asking for something, but they don’t know how to ask those of us building the technology. Or they don’t understand the implications of asking for something like “absolutely zero data loss” to be implemented.

The official topic this month is:

What issues have you had in interacting with the business to get your job done.

Post your answer on Dec 14, 2010, based on GMT time, make sure a trackback or link appears in the comments for this blog, and I’ll look forward to reading what issues you have had to work through.