Get short, timely messages from SqlAsylum.

Twitter is a rich source of instantly updated information. It's easy to stay updated on an incredibly wide variety of topics. Join today and follow @SqlAsylum.

Get updates via SMS by texting follow SqlAsylum to 40404 in the United States
Codes for other countries

Two-way (sending and receiving) short codes:
Country Code For customers of
Australia
  • 0198089488 Telstra
Canada
  • 21212 (any)
United Kingdom
  • 86444 Vodafone, Orange, 3, O2
Indonesia
  • 89887 AXIS, 3, Telkomsel
Ireland
  • 51210 O2
India
  • 53000 Bharti Airtel, Videocon
Jordan
  • 90903 Zain
New Zealand
  • 8987 Vodafone, Telecom NZ
United States
  • 40404 (any)

SqlAsylum

  1. @sqlschizo I just know you too well. :) need to get some sushi before you skip town again. :) I'll write you offline
  2. @tjaybelt ya @sqlschizo can never remember my twitter handle. :) Even though i helped him come up with his. :)
  3. @sqlschizo I'm always worried about you. :)
  4. that was weird. first time I look at my twitter stream all day and @tjaybelt and @sqlschizo are talking about me? Very strange. :)
  5. I've got a ticket to the #hadoop summit coming up in june hadoopsummit.org i can't go if you need a ticket to this let me know
  6. @mrdenny @SQLRockstar no excuses. :-) not a real sql event without jaeger. :-)
  7. @SQLRockstar I highly doubt that. :-)
  8. @SQLRockstar how dare you not have jaeger. On the table. :-)
  9. @nodns You are implying @sqlrockstar stops drinking. :)
  10. @utahGeekevents is officially a 501c(3) with the Fed govt! Huge step a year in the making! :)
  11. When Perf tuning a query everything is relative. You would think a decrease of 22 seconds is good. Not this time.
  12. @craigber we would have to work out a schedule for the room. :) in 1 hour bursts or something. :)
  13. @denisemc06 I may be attending #hadoop summit looking into it right now
  14. @sunnyhunt oooh love the minibar addition. :) gotta have that shot after a tough workout. :)
  15. I think companies should put in anger/frustration rooms to vent safely when you have to deal with questionable code. :-)
  16. @jdgonzalez 16 actually. :)
  17. Dear Dev, yes pulling 600k+ rows across sql servers on every stored proc call will take time and resources. #justsaying :)
  18. I think it's a Mai Tai sort of evening. :) Too bad i have studying/work to do this evening. :)