Are the posted questions getting worse?

  • rodjkidd (3/10/2015)


    ChrisM@Work (3/10/2015)


    rodjkidd (3/10/2015)


    Eirikur Eiriksson (3/10/2015)


    rodjkidd (3/9/2015)


    Eirikur Eiriksson (3/9/2015)


    Grant Fritchey (3/9/2015)


    Great seeing everyone this week at SQLBits.

    And, I got to meet Gianluca and Eirikur for the very first time. Total pleasure gentlemen. By the way, Gianluca is a giant.

    Pleasure meeting you Grant and many others, not certain how I missed Gianluca or by Grant's description, GiganteLuca:-D

    😎

    Eirikur I didn't know you were there this year. I realised I'd missed meeting Gianluca by the end of the day. It was very busy being on the helper / volunteer side of things!

    Legs still ache. But then I also showed a couple of people round parts of London and stood at a concert Saturday night. The seated tickets had sold out.

    Oh well next time at SQL Bits or at a SQL Sat I guess!

    Hope everyone had a blast. It was really good fun and I learnt a lot.

    Cheers,

    Rodders...

    he he, you probably didn't recognize me in my "office bloke" disguise:-D

    😎

    Ha probably. Plus it is busy on the Saturday and I was late ish getting there...

    Rodders...

    Were you there thursday Rodders? I saw Rich D, Christian B & Karl G and bumped into Steve and Grant and also Gail, piccies later. I'm really sorry I missed Eirikur the Iceman and Gianormous. Spent some time chatting with Sandip about his session at Bits last year.

    For those of you who don't know, Grant stepped up to the plate when Benjamin Nevarez was caught up in transit somewhere and gave an off-the-cuff talk at about 3 minutes notice.

    Cojones of steel.

    Ha. Yes but I was Allan Mitchell and Lara's room monitor. As it was a training day the breaks were at different times to the regular sessions. And I wasn't on registration as it was decided that training day Room monitors would go straight to the room to make sure everything was ship shape. And lunch only overlapped for 30 minutes! Doh! Gianormous (:-) ) was only there Saturday as far as I know. So if you did see him on Thursday then you should have also done the lottery!

    Then headed off to Shepherds Bush for the Trevor Horn gig. Seal was ill but turned up to say sorry. They even did Relax which was a big surprise. And Soon by Yes. which then lead into Owner Of a Lonely Heart. For those who known about these things - Geoff Downes was the guest Keyboard player. So I did hold out a little for for a track from Drama. But no. Obviously as Trevor and Geoff were Buggles the two songs from Buggles got the biggest cheers.

    Back to SQL Bits...

    Only twigged on Saturday that I missed you due to the breaks being staggered!

    Benjamin wasn't actually down to speak. he had cancelled / declined a while ago. But it slipped through on the program. So he didn't pull a no show, but it was an admin failure.

    Having said that.... GRANT! You HERO!

    Stepping in, un-prepared, within minutes. Plus you did a hour slot followed by a double slot on the Saturday. Dear god man I knew you were good, but above and beyond the call of duty. :w00t: 😀

    So after saying all that I feel I now need to insult you about 3 or 4 times the next time we meet to address the balance - people worry when I am serious for too long 😉

    Oh will be posting the pictures here:

    https://www.flickr.com/photos/127113040@N04/with/16562799077/

    I've put the ones I tweeted yesterday up, but over the next few days I will concentrate on the party / fancy dress ones. Then go back to the start... Didn't get any of the Thames cruise - too busy chatting to everyone! :-O

    Cheers,

    Rodders...

    Looking forward to the insults.

    Thanks.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • SqlSanctum (3/9/2015)


    jasona.work (3/9/2015)


    SQLRNNR (3/9/2015)


    jasona.work (3/7/2015)


    Turns out, Public by default does not have CONNECT SQL. So I was thinking I could grant the privilege to Public, then revoke it from the individual accounts.

    Did you use the public / "everyone" role, or did you end on creating a new role with the requisite permissions?

    The public role should have as few permissions as possible.

    As most of our servers are still SQL2008R2, we couldn't create a custom server role to handle this. As of right now, this is first privilege that isn't a default that's been added to Public, so we're keeping the priveleges low.

    On our new SQL2012 boxes, I'll have to think about how to handle this. A custom role would be the better way (even if it is just for CONNECT SQL,) but would also result in more paperwork (yes, to add a server role to satisfy a mandatory STIG check, I'd have to get approval...) Plus having to remember to add any new users to that custom role any time I add one...

    Pluses and minuses either way, it's just a matter of totalling them up and picking which way to jump.

    STIG compliance woes! We use a custom Connect SQL role for 2012 boxes and public has Connect SQL for 2008 boxes just like your idea. Initial creation is handled by scripts each time a new server gets built then checked by policy daily.

    So, thanks to your comment, now I've started poking around in Policy-Based-Management to keep an eye on this...

    Actually have the basis of an executeSQL check, but it runs against all logins, so I'm starting to lean towards just using an Agent job. Or, seeing as we don't have that much "churn" in our logins, just manually checking once a month or so...

  • jasona.work (3/10/2015)


    SqlSanctum (3/9/2015)


    jasona.work (3/9/2015)


    SQLRNNR (3/9/2015)


    jasona.work (3/7/2015)


    Turns out, Public by default does not have CONNECT SQL. So I was thinking I could grant the privilege to Public, then revoke it from the individual accounts.

    Did you use the public / "everyone" role, or did you end on creating a new role with the requisite permissions?

    The public role should have as few permissions as possible.

    As most of our servers are still SQL2008R2, we couldn't create a custom server role to handle this. As of right now, this is first privilege that isn't a default that's been added to Public, so we're keeping the priveleges low.

    On our new SQL2012 boxes, I'll have to think about how to handle this. A custom role would be the better way (even if it is just for CONNECT SQL,) but would also result in more paperwork (yes, to add a server role to satisfy a mandatory STIG check, I'd have to get approval...) Plus having to remember to add any new users to that custom role any time I add one...

    Pluses and minuses either way, it's just a matter of totalling them up and picking which way to jump.

    STIG compliance woes! We use a custom Connect SQL role for 2012 boxes and public has Connect SQL for 2008 boxes just like your idea. Initial creation is handled by scripts each time a new server gets built then checked by policy daily.

    So, thanks to your comment, now I've started poking around in Policy-Based-Management to keep an eye on this...

    Actually have the basis of an executeSQL check, but it runs against all logins, so I'm starting to lean towards just using an Agent job. Or, seeing as we don't have that much "churn" in our logins, just manually checking once a month or so...

    You can make a Target Condition that will only include the logins you need to check, or exclude the logins you never want to check. I'd say that since you are probably monitoring new logins that are created too, you could monitor this less, but verifying everything regularly saves sanity when audits come up. Jobs would probably work just as well, and are easier to make. We went with PBM I think just to force us to learn it.

  • ChrisM@Work (3/10/2015)

    For those of you who don't know, Grant stepped up to the plate when Benjamin Nevarez was caught up in transit somewhere and gave an off-the-cuff talk at about 3 minutes notice.

    Cojones of steel.

    Not the first time Grant has done that. He's stepped up to fill-in sessions at a couple of SQLSaturday's I've been involved in.

  • SQLRNNR (3/9/2015)


    Jack Corbett (3/9/2015)


    Grant Fritchey (3/9/2015)


    By the way, Gianluca is a giant.

    So this means if and when I meet Gianluca he'll have to be seated for us to see eye to eye.:-P

    Well, he might have to be laying down for that to happen...:-D

    Ouch, that's a low blow 😀

  • Jack Corbett (3/10/2015)


    SQLRNNR (3/9/2015)


    Jack Corbett (3/9/2015)


    Grant Fritchey (3/9/2015)


    By the way, Gianluca is a giant.

    So this means if and when I meet Gianluca he'll have to be seated for us to see eye to eye.:-P

    Well, he might have to be laying down for that to happen...:-D

    Ouch, that's a low blow 😀

    Operative word being low :hehe:;-):w00t:

    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

  • SQLRNNR (3/10/2015)


    Jack Corbett (3/10/2015)


    SQLRNNR (3/9/2015)


    Jack Corbett (3/9/2015)


    Grant Fritchey (3/9/2015)


    By the way, Gianluca is a giant.

    So this means if and when I meet Gianluca he'll have to be seated for us to see eye to eye.:-P

    Well, he might have to be laying down for that to happen...:-D

    Ouch, that's a low blow 😀

    Operative word being low :hehe:;-):w00t:

    Take the high road, Jack. Just take the high road.

    (duck)

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • Brandie Tarvin (3/10/2015)


    SQLRNNR (3/10/2015)


    Jack Corbett (3/10/2015)


    SQLRNNR (3/9/2015)


    Jack Corbett (3/9/2015)


    Grant Fritchey (3/9/2015)


    By the way, Gianluca is a giant.

    So this means if and when I meet Gianluca he'll have to be seated for us to see eye to eye.:-P

    Well, he might have to be laying down for that to happen...:-D

    Ouch, that's a low blow 😀

    Operative word being low :hehe:;-):w00t:

    Take the high road, Jack. Just take the high road.

    (duck)

    Tsk tsk, don't belittle Jack.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Koen Verbeeck (3/10/2015)


    Brandie Tarvin (3/10/2015)


    SQLRNNR (3/10/2015)


    Jack Corbett (3/10/2015)


    SQLRNNR (3/9/2015)


    Jack Corbett (3/9/2015)


    Grant Fritchey (3/9/2015)


    By the way, Gianluca is a giant.

    So this means if and when I meet Gianluca he'll have to be seated for us to see eye to eye.:-P

    Well, he might have to be laying down for that to happen...:-D

    Ouch, that's a low blow 😀

    Operative word being low :hehe:;-):w00t:

    Take the high road, Jack. Just take the high road.

    (duck)

    Tsk tsk, don't belittle Jack.

    He can't help but be little.

    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

  • Brandie Tarvin (3/10/2015)


    SQLRNNR (3/10/2015)


    Jack Corbett (3/10/2015)


    SQLRNNR (3/9/2015)


    Jack Corbett (3/9/2015)


    Grant Fritchey (3/9/2015)


    By the way, Gianluca is a giant.

    So this means if and when I meet Gianluca he'll have to be seated for us to see eye to eye.:-P

    Well, he might have to be laying down for that to happen...:-D

    Ouch, that's a low blow 😀

    Operative word being low :hehe:;-):w00t:

    Take the high road, Jack. Just take the high road.

    (duck)

    He has trouble reaching it...

    Wayne
    Microsoft Certified Master: SQL Server 2008
    Author - SQL Server T-SQL Recipes


    If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
    Links:
    For better assistance in answering your questions
    Performance Problems
    Common date/time routines
    Understanding and Using APPLY Part 1 & Part 2

  • Wow! I have little to say.

  • Jack Corbett (3/10/2015)


    Wow! I have little to say.

    😀

    You rock!

    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

  • SqlSanctum (3/10/2015)


    jasona.work (3/10/2015)


    SqlSanctum (3/9/2015)


    jasona.work (3/9/2015)


    SQLRNNR (3/9/2015)


    jasona.work (3/7/2015)


    Turns out, Public by default does not have CONNECT SQL. So I was thinking I could grant the privilege to Public, then revoke it from the individual accounts.

    Did you use the public / "everyone" role, or did you end on creating a new role with the requisite permissions?

    The public role should have as few permissions as possible.

    As most of our servers are still SQL2008R2, we couldn't create a custom server role to handle this. As of right now, this is first privilege that isn't a default that's been added to Public, so we're keeping the priveleges low.

    On our new SQL2012 boxes, I'll have to think about how to handle this. A custom role would be the better way (even if it is just for CONNECT SQL,) but would also result in more paperwork (yes, to add a server role to satisfy a mandatory STIG check, I'd have to get approval...) Plus having to remember to add any new users to that custom role any time I add one...

    Pluses and minuses either way, it's just a matter of totalling them up and picking which way to jump.

    STIG compliance woes! We use a custom Connect SQL role for 2012 boxes and public has Connect SQL for 2008 boxes just like your idea. Initial creation is handled by scripts each time a new server gets built then checked by policy daily.

    So, thanks to your comment, now I've started poking around in Policy-Based-Management to keep an eye on this...

    Actually have the basis of an executeSQL check, but it runs against all logins, so I'm starting to lean towards just using an Agent job. Or, seeing as we don't have that much "churn" in our logins, just manually checking once a month or so...

    You can make a Target Condition that will only include the logins you need to check, or exclude the logins you never want to check. I'd say that since you are probably monitoring new logins that are created too, you could monitor this less, but verifying everything regularly saves sanity when audits come up. Jobs would probably work just as well, and are easier to make. We went with PBM I think just to force us to learn it.

    In our case, we'd need to be checking every login, every time, so I'm thinking an Agent job. Possibly set it to run once a week or so, and dump its' results to a table in a DB with a date stamp so we could, if needed, get an idea *when* a login got flipped...

  • SQLRNNR (3/10/2015)


    Jack Corbett (3/10/2015)


    Wow! I have little to say.

    😀

    You rock!

    I'd say he's clearly the bigger man 🙂

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Jack Corbett (3/10/2015)


    Wow! I have little to say.

    Quick question, this is a normal size Strat in your picture then?

    😎

Viewing 15 posts - 47,776 through 47,790 (of 66,712 total)

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