February 10, 2010 at 7:21 pm
That would be the one - NCIS.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
February 10, 2010 at 7:39 pm
CirquedeSQLeil (2/10/2010)
...I thought the SB one was amusing - and informative.
The black list one - I think a good point was made. But I think it is mostly for anybody coming after the fact.
That's right, and that is why I made that post, even though it was after the fact. One thing that I am extremely sensitive to is people who try to make good people feel guilty just for being good people, or worse, for not being "good enough". In my experience, this is nothing to do with personal opinions, or ethical differences. It is just a blatant attempt to gain leverage through emotional manipulation and I have seen way, way too many good people abused by it.
My rule of thumb is, you don't get to talk trash on good people unless you've been walking the walk yourself (and have proof of it). And in my experience, such people generally don't talk trash themselves.
I hope you didn't take my comment wrong - I made it in jest.
No worries, that's how I took it. 🙂
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
February 10, 2010 at 7:44 pm
CirquedeSQLeil (2/10/2010)
RBarryYoung (2/10/2010)
Steve Jones - Editor (2/10/2010)
Barry,That response reminded me of the Super Bowl ad with everyone smacking the backs of people's heads.
which one was that? I can't seem to find it.
Replacing the handshake with slapping the back of the head. Can't remember what company though.
Ah, OK, I found it now.
Heh, good one Steve, very appropriate. In Philly, we call that "upside yo head." :w00t:
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
February 10, 2010 at 9:37 pm
RBarryYoung (2/10/2010)
Lynn Pettis (2/10/2010)
RBarryYoung (2/10/2010)
Lynn Pettis (2/10/2010)
Any tips on trying to debug why a SB activated stored proc doesn't do everything it is supposed to but when run in debug mode from SSMS it runs correctly?At this point I'm just looking for tips. If I find myself hitting the wall too many times, I'll come back with more details.
Using SQL Server 2008 Enterprise Edition if that helps with the tips.
Yep, two tips
1) Goto my blog site and download my presentation "TheTop Ten Reasons You Aren't already using Service Broker", or "Top 10 Fixes for your first Service Broker project". It's actually got 15 tips in it, so it's more of a mega-tip.
2) The symptom that you are describing is most often caused by the restricted security context that the Activation Procedure runs under. In particular it typically cannot access non-public resources in other databases without some special setup.
Thank you, Barry. I will look at those this evening while Kylie is at church and I'm sitting at McD's.
Heh. Poor guy. Both of those places are better than having to read some junk that I wrote. 😀
Okay Barry, thank you. Your powerpoint plus ALZDBA's article on SSC helped. When I got home I remoted into one of my desktop systems at work, ALTERed the database in question setting trustworthy on, and the activation procedure worked as it was designed. Just more info for my article as well.
Definitely learning more about SB at this time than when I first was looking at it for other purposes (which I still want to do as well).
Again, thanks. That one would probably kept me stumped for quite a while.
February 10, 2010 at 10:26 pm
Lynn Pettis (2/10/2010)
...Okay Barry, thank you. Your powerpoint plus ALZDBA's article on SSC helped. When I got home I remoted into one of my desktop systems at work, ALTERed the database in question setting trustworthy on, and the activation procedure worked as it was designed. Just more info for my article as well.
Definitely learning more about SB at this time than when I first was looking at it for other purposes (which I still want to do as well).
Again, thanks. That one would probably kept me stumped for quite a while.
Glad it worked out for you. 🙂
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
February 11, 2010 at 1:24 am
RBarryYoung (2/10/2010)
1) Goto my blog site and download my presentation "TheTop Ten Reasons You Aren't already using Service Broker", or "Top 10 Fixes for your first Service Broker project". It's actually got 15 tips in it, so it's more of a mega-tip.2) The symptom that you are describing is most often caused by the restricted security context that the Activation Procedure runs under. In particular it typically cannot access non-public resources in other databases without some special setup.
Barry, have you ever used Service Broker and triggers to move data from one DB to another? If so, can I mail you and chat about pros, cons and gotchas?
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
February 11, 2010 at 1:31 am
GilaMonster (2/11/2010)
RBarryYoung (2/10/2010)
1) Goto my blog site and download my presentation "TheTop Ten Reasons You Aren't already using Service Broker", or "Top 10 Fixes for your first Service Broker project". It's actually got 15 tips in it, so it's more of a mega-tip.2) The symptom that you are describing is most often caused by the restricted security context that the Activation Procedure runs under. In particular it typically cannot access non-public resources in other databases without some special setup.
Barry, have you ever used Service Broker and triggers to move data from one DB to another? If so, can I mail you and chat about pros, cons and gotchas?
I sure have, so feel free to email me. One caveat, it's my bedtime here (3:30am), and I have a medical procedure tomorrow, so I won't see your stuff until late afternoon at best.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
February 11, 2010 at 2:55 am
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
February 11, 2010 at 3:10 am
February 11, 2010 at 3:52 am
The 'sigh' is a link to today's featured article. I'm away from home an unable to reply as I would wish. Just venting on The Thread a bit really I suppose 😎
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
February 11, 2010 at 4:12 am
Paul White (2/11/2010)
The 'sigh' is a link to today's featured article. I'm away from home an unable to reply as I would wish. Just venting on The Thread a bit really I suppose 😎
I went (very quickly) through the article you linked, and I can't find anything wrong. It might just be my ignorance speaking, anyway... I suppose you disagree with some point there, don't you?
-- Gianluca Sartori
February 11, 2010 at 4:28 am
I can't see anything catastrophically wrong. Not like the 'fixing of a suspect DB earlier this week'
Yes, the index diagram is slightly incorrect (the root has a single page), the 'exploded' view of the index entries is missing lots of stuff (row headers, page pointers, clustered index key/RID, etc) and his space saving calcs are miles off (commented on already in the discussion), but it's not a train wreck of an article.
The one thing that does bug me is that there's no mention of the tradeoffs involved in wider indexes. More space in the data file, more time to backup, more impact in inserts/updates. I suppose he's taking the point of you *are* covering this query, see how much more efficient it is with Include columns rather than putting everything into the key.
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
February 11, 2010 at 4:44 am
No - I didn't mean to suggest that the article is terrible (certainly not on the scale of 'suspect db') - just that it's frustrating being connected through what appears to be wireless dial-up - when I get a connection at all.
I would like to correct the maths fully (it is pretty central to the article's point) and add some comments about maintaining balanced trees and so on. Mentioning the trade-offs in the article would have been a nice INCLUDE too, possibly even a KEY point 😀
The article itself is nicely presented, it could just have been so much better. A missed-opportunity-plus-carp-wireless 'sigh' then.
this is my third attempt to post this
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
February 11, 2010 at 6:05 am
Gail/Jason, kudos for not going off on this guy, I don't think he even tried Jason's suggestion, just totally disbelieved him.
---------------------------------------------------------
How best to post your question[/url]
How to post performance problems[/url]
Tally Table:What it is and how it replaces a loop[/url]
"stewsterl 80804 (10/16/2009)I guess when you stop and try to understand the solution provided you not only learn, but save yourself some headaches when you need to make any slight changes."
February 11, 2010 at 6:28 am
I got the 2009 Pass Summit Session Recording DVDs... Yea..!!!!
-Roy
Viewing 15 posts - 11,326 through 11,340 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply