The SQL Saturday Thread

  • Steve Jones - SSC Editor - Monday, May 21, 2018 9:12 AM

    Heading the SQL Sat LA in a few weeks.

    The only other one I have on the agenda now for the US is Pittsburgh. Louisville/BatonRouge/Sioux Falls/Lincoln up in the air, depending on family plans. Oslo/Cambridge on my list if I get picked.

    You're going to Pittsburgh this year?  We'll finally get to meet in person.  Jeff, you and I will have to get together for a drink.

  • Steve Jones - SSC Editor - Monday, May 21, 2018 9:12 AM

    Heading the SQL Sat LA in a few weeks.

    The only other one I have on the agenda now for the US is Pittsburgh. Louisville/BatonRouge/Sioux Falls/Lincoln up in the air, depending on family plans. Oslo/Cambridge on my list if I get picked.

    I'm looking forward to seeing you here.

    Is there a checklist for attendees and organizers that you find helpful?

    412-977-3526 call/text

  • Ed Wagner - Monday, May 21, 2018 9:37 AM

    Steve Jones - SSC Editor - Monday, May 21, 2018 9:12 AM

    Heading the SQL Sat LA in a few weeks.

    The only other one I have on the agenda now for the US is Pittsburgh. Louisville/BatonRouge/Sioux Falls/Lincoln up in the air, depending on family plans. Oslo/Cambridge on my list if I get picked.

    You're going to Pittsburgh this year?  We'll finally get to meet in person.  Jeff, you and I will have to get together for a drink.

    Submitted, we'll see.

  • robert.sterbal 56890 - Monday, May 21, 2018 9:43 AM

    I'm looking forward to seeing you here.

    Is there a checklist for attendees and organizers that you find helpful?

    Checklist for?

    Nothing for attendees. I know some people have written posts on things you consider, but really, just be a good citizen, listen, ask question, shake hands.

  • Steve Jones - SSC Editor - Monday, May 21, 2018 9:12 AM

    Heading the SQL Sat LA in a few weeks.

    The only other one I have on the agenda now for the US is Pittsburgh. Louisville/BatonRouge/Sioux Falls/Lincoln up in the air, depending on family plans. Oslo/Cambridge on my list if I get picked.

    Awesome!  It's been a while since I've gotten to see you in person!  I've also submitted for Denver for this year for a double session on the Index Maintenance thing I've been posting about.  Coerce Grant into showing up an we'll have a good ol' "home coming" of almost ancient friendships!

    --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)

  • Hoping I'll make Denver. The timing is not great with a potential family conflict.We'll see.

  • Ray K - Sunday, May 20, 2018 6:37 PM

    Jeff Moden - Saturday, May 19, 2018 3:08 PM

    I've submitted the following 2 abstracts to Columbus (OH), Indianapolis, Denver, and Pittsburgh.

    “Black Arts†Index Maintenance #1: How the “Best Practice†Methods are Silently Killing Performance

    Most people don’t know it but the current “Best Practice†Methods are actually the leading cause of perpetual logical and physical fragmentation, costly and continuous “Bad†page splits, comparatively insane amounts of log file generation and, in an interesting “Catch 22â€, the whole reason for why we have to do so much index maintenance.

    This isn’t your typical presentation on Index Maintenance.

    In this first of two back-to-back sessions on the subject, we’ll explore what happens to an index in the first year of its life for four different common Fill Factors along with how “Best Practice†methods executed once per week and once per day have their way with you, your indexes, your log files, wasted memory, and the performance of your code even if it’s perfect code.

    “Black Arts†Index Maintenance #2: Better Methods that Can Actually Prevent Fragmentation for Weeks.

    Most people don’t know it but the current “Best Practice†Methods are actually the leading cause of perpetual logical and physical fragmentation, costly and continuous “Bad†page splits, comparatively insane amounts of log file generation and, in an interesting “Catch 22â€, the whole reason for why we have to do so much index maintenance.

    This isn’t your typical presentation on Index Maintenance.

    In this second of two back-to-back sessions, we’ll learn of three incredibly easy modifications to your Index Maintenance routines to actually prevent fragmentation for weeks rather than perpetuating it,  virtually eliminate “Bad†page splits, reduce wasted memory, make your log file and log file backups a whole lot more happy, and increase the overall performance of even perfect code.

    We’ll also learn that no simple method is a panacea and what to do about the horror of expAnsive updates.

    I really wanted to go to many others like KY, TN, Albany, Madison, and Sioux Falls, but I'm getting a bit old for 10 hour drives each way and, since I have no sponsors (and frankly don't know why anyone would sponsor me because I don't use 3rd party products except for occasional use of SQL Compare), can only afford about 1 plane trip a year.

    We'd love to have you in Albany!  There's still a couple of weeks left to submit!

    Thank you kindly and it would be an honor.  Sadly, I don't believe I'll be able to make Albany.  It's on the same day as Columbus, OH and, like I said, the 10 hour drive would be a little tough on this ol' man and, not being sponsored, I can only afford one plane trip per year and this year, that will be (hopefully) Denver.  Really hope they pick my sessions because there are a couple of people out there that are on my bucket list plus I've never been to Denver.

    Of course, none of this is final because I just submitted abstracts.

    --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)

  • Steve Jones - SSC Editor - Monday, May 21, 2018 9:47 AM

    robert.sterbal 56890 - Monday, May 21, 2018 9:43 AM

    I'm looking forward to seeing you here.

    Is there a checklist for attendees and organizers that you find helpful?

    Checklist for?

    Nothing for attendees. I know some people have written posts on things you consider, but really, just be a good citizen, listen, ask question, shake hands.

    The group in Pittsburgh runs just fine without me. I'll just stop by to catch the speakers and topics that catch my attention.

    412-977-3526 call/text

  • Jeff Moden - Monday, May 21, 2018 9:59 AM

    Ray K - Sunday, May 20, 2018 6:37 PM

    Jeff Moden - Saturday, May 19, 2018 3:08 PM

    I've submitted the following 2 abstracts to Columbus (OH), Indianapolis, Denver, and Pittsburgh.

    “Black Arts†Index Maintenance #1: How the “Best Practice†Methods are Silently Killing Performance

    Most people don’t know it but the current “Best Practice†Methods are actually the leading cause of perpetual logical and physical fragmentation, costly and continuous “Bad†page splits, comparatively insane amounts of log file generation and, in an interesting “Catch 22â€, the whole reason for why we have to do so much index maintenance.

    This isn’t your typical presentation on Index Maintenance.

    In this first of two back-to-back sessions on the subject, we’ll explore what happens to an index in the first year of its life for four different common Fill Factors along with how “Best Practice†methods executed once per week and once per day have their way with you, your indexes, your log files, wasted memory, and the performance of your code even if it’s perfect code.

    “Black Arts†Index Maintenance #2: Better Methods that Can Actually Prevent Fragmentation for Weeks.

    Most people don’t know it but the current “Best Practice†Methods are actually the leading cause of perpetual logical and physical fragmentation, costly and continuous “Bad†page splits, comparatively insane amounts of log file generation and, in an interesting “Catch 22â€, the whole reason for why we have to do so much index maintenance.

    This isn’t your typical presentation on Index Maintenance.

    In this second of two back-to-back sessions, we’ll learn of three incredibly easy modifications to your Index Maintenance routines to actually prevent fragmentation for weeks rather than perpetuating it,  virtually eliminate “Bad†page splits, reduce wasted memory, make your log file and log file backups a whole lot more happy, and increase the overall performance of even perfect code.

    We’ll also learn that no simple method is a panacea and what to do about the horror of expAnsive updates.

    I really wanted to go to many others like KY, TN, Albany, Madison, and Sioux Falls, but I'm getting a bit old for 10 hour drives each way and, since I have no sponsors (and frankly don't know why anyone would sponsor me because I don't use 3rd party products except for occasional use of SQL Compare), can only afford about 1 plane trip a year.

    We'd love to have you in Albany!  There's still a couple of weeks left to submit!

    Thank you kindly and it would be an honor.  Sadly, I don't believe I'll be able to make Albany.  It's on the same day as Columbus, OH and, like I said, the 10 hour drive would be a little tough on this ol' man and, not being sponsored, I can only afford one plane trip per year and this year, that will be (hopefully) Denver.  Really hope they pick my sessions because there are a couple of people out there that are on my bucket list plus I've never been to Denver.

    Of course, none of this is final because I just submitted abstracts.

    Jeff, if you are at Denver I will be sure to be there as well.

  • Steve Jones - SSC Editor - Monday, May 21, 2018 9:47 AM

    Ed Wagner - Monday, May 21, 2018 9:37 AM

    Steve Jones - SSC Editor - Monday, May 21, 2018 9:12 AM

    Heading the SQL Sat LA in a few weeks.

    The only other one I have on the agenda now for the US is Pittsburgh. Louisville/BatonRouge/Sioux Falls/Lincoln up in the air, depending on family plans. Oslo/Cambridge on my list if I get picked.

    You're going to Pittsburgh this year?  We'll finally get to meet in person.  Jeff, you and I will have to get together for a drink.

    Submitted, we'll see.

    I've submitted to Pittsburgh as well!  If I get picked, hopefully, I'll see you there!

    Jeff -- I hear what you're saying about 10 hour drives -- if I do get picked, I'll probably take Amtrak instead of driving out!

    +--------------------------------------------------------------------------------------+
    Check out my blog at https://pianorayk.wordpress.com/

  • Lynn Pettis - Monday, May 21, 2018 10:29 AM

    Jeff, if you are at Denver I will be sure to be there as well.

    Awesome.  You're one of the folks on my bucket list.  I couldn't make Colorado Springs this year and so I went with the next best opportunity of Denver.  Now all I need is to get picked to present.

    --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)

  • Ray K - Monday, May 21, 2018 11:44 AM

    Steve Jones - SSC Editor - Monday, May 21, 2018 9:47 AM

    Ed Wagner - Monday, May 21, 2018 9:37 AM

    Steve Jones - SSC Editor - Monday, May 21, 2018 9:12 AM

    Heading the SQL Sat LA in a few weeks.

    The only other one I have on the agenda now for the US is Pittsburgh. Louisville/BatonRouge/Sioux Falls/Lincoln up in the air, depending on family plans. Oslo/Cambridge on my list if I get picked.

    You're going to Pittsburgh this year?  We'll finally get to meet in person.  Jeff, you and I will have to get together for a drink.

    Submitted, we'll see.

    I've submitted to Pittsburgh as well!  If I get picked, hopefully, I'll see you there!

    Jeff -- I hear what you're saying about 10 hour drives -- if I do get picked, I'll probably take Amtrak instead of driving out!

    Heh... Amtrack.  I don't know if things have changed or not but the last time I checked it took a lot longer than driving and a fair number of train changes to get there from here.

    --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)

  • Jeff Moden - Monday, May 21, 2018 12:25 PM

    Ray K - Monday, May 21, 2018 11:44 AM

    Steve Jones - SSC Editor - Monday, May 21, 2018 9:47 AM

    Ed Wagner - Monday, May 21, 2018 9:37 AM

    Steve Jones - SSC Editor - Monday, May 21, 2018 9:12 AM

    Heading the SQL Sat LA in a few weeks.

    The only other one I have on the agenda now for the US is Pittsburgh. Louisville/BatonRouge/Sioux Falls/Lincoln up in the air, depending on family plans. Oslo/Cambridge on my list if I get picked.

    You're going to Pittsburgh this year?  We'll finally get to meet in person.  Jeff, you and I will have to get together for a drink.

    Submitted, we'll see.

    I've submitted to Pittsburgh as well!  If I get picked, hopefully, I'll see you there!

    Jeff -- I hear what you're saying about 10 hour drives -- if I do get picked, I'll probably take Amtrak instead of driving out!

    Heh... Amtrack.  I don't know if things have changed or not but the last time I checked it took a lot longer than driving and a fair number of train changes to get there from here.

    LOL...  I already looked.  For me, it'd only be one train change.  ALB -> NYC -> PIT.

    Yes, it would be longer than driving, but I'd rather be relaxed for 9 hours than have to be uncomfortable behind the wheel for 8.

    Besides, I like trains! 🙂

    +--------------------------------------------------------------------------------------+
    Check out my blog at https://pianorayk.wordpress.com/

  • Just found out my 2 session presentation on "Black Arts" Index Maintenance has been accepted for Columbus, OH on July 28th.  Really looking forward to it.

    --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)

  • Congrats.

    I'm in for Louisville.

    Submissions out for:
    Baton Rouge
    Cambridge
    Pittsburgh

    Trying to decide on Orlando or Minn
    Would like to get  to Lincoln.

Viewing 15 posts - 46 through 60 (of 165 total)

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