Tag: syndicated

  • Customizing SSMS–Results

    This is a short series on some customizations in SSMS to make it visually more appealing.

    As a presenter, I’ve learned how to change the way Management Studio (SSMS) looks to make it easier for people to see the screen on a projector. I had wrongly assumed that so many people knew many of these tricks, which is a poor attitude on my part. That should be especially apparent as I saw a presentation recently where the speaker didn’t know how to make things easier to see.

    In a previous post I talked about changing the query font size. In this post we’ll look at result sizes.

    The Defaults

    This is what I see, and it’s not easy to read.

    Capture_009

    The results are much smaller than the query itself. How can we change this and make things easier to read?

    I wrote about one way: using results to text. This works well, but it isn’t the best solution for everyone, and you still want to change the size of your results. The technique I’ll show you works for that as well.

    Customization

    If you go to the Tools | Options menu, in the Fonts tab as I showed in the last post, you’ll find there’s a drop down titled “Show settings for:” at the top. If you select Grid results, you can change the font settings.

    Capture_006

    The default is 8, and I usually up that a bit.

    Capture_007

    Once that is done, you click OK, and get this note:

    Capture_008

    Make sure your tabs are saved, since you need to restart SSMS. Once you do, your results will be much easier to read.

    Capture_005

    Note that in the drop down for settings, there is an item for “Results to text”. If you change that, your text results will be larger.

  • Disabling Resource Governor

    I had known that the Resource Governor is always running in modern versions of SQL Server. It’s core to the operation of the SQLOS, though it can’t be used to do anything unless it is enabled.

    You can read more about it if you have Enterprise Edition, and I’ve thought it was a good start to controlling and throttling the resources inside SQL Server. I’d like to see it expanded, and I do like the CAP addition in 2012.

    However I wasn’t aware you could prevent someone from enabling Resource Governor. Apparently you can, as shown in this blog: Disabling Resource Governor permanently (somewhat). Amit Bansal shows that if you set trace flag 8040, the Resource Governor cannot be enabled. This prevents changes by junior administrators, developers, etc. that might not be aware of the consequences of their actions.

    Personally for me, I’m not sure I like this. To me this is a case where you don’t have trust among your staff, or good communication, or perhaps something else. None of those are good situations.

    I don’t know that I’d ever use this, but you can read Amit’s post for more details.

    Note that this doesn’t remove Resource Governor, and your DAC still resides in the internal pool, which always has guaranteed resources.

  • Thirty Hours at Home

    This is a busy travel week for me, and one of those times that stresses out everyone in the household. I attended SQL Saturday #197 – Omaha over the weekend, arriving home Sunday morning from my trip. I had a good time at the event, my first time to Omaha, and would like to go back again sometime.

    However it’s a quick turnaround for me. Fortunately I have packing down to a science since I’m leaving today at 2:00 for Las Vegas and the first SQL Intersection conference. I have two talks to deliver on Tuesday and a few sessions I’d like to see Wednesday before I head home again.

    Back in time to cook a couple meals (and extra leftovers) for the family and spend a day with everyone before heading back out of town. These are tough times, and it’s a lot of support from the family that allows me to do this.

    I’ll have the same type of turnaround at the end of the month between SQL Saturday #175 – Fargo and SQL Bits.

    I may have to limit some trips later in the year after this month, so please don’t be offended if I decline any offers to speak.

  • Reminders and Rehearsal

    I’ve spoken at quite a few SQL Saturday events. I won’t hit 50 this year, like Kevin Boles, but by my count, I’ve been to 21, with 4 or 5 more coming this year.  I have no idea when I’ll get to 50, but I hope I do.

    Capture_028

    That’s in addition to other events, which will likely bring my 2013 total to close to 15 events, similar to what I’ve done the last few years. That doesn’t seem like a lot, maybe 1 every six weeks, but I end up doing multiple talks, on multiple subjects sometimes. There was a stretch late last year where I did 12 talks in 7 different areas in about 3 weeks. It was slightly confusing for me.

    Yesterday I received an email from SQL Saturday #197 – Omaha, which had the schedule in it. I’d glanced at it before, and had seen I was giving my Encryption Primer talk, but this time as I scrolled down, I saw my name at the end.

    sqlsat197

    Hmmm, that didn’t say “The Encryption Primer”. I’m glad I looked and double checked the schedule because I’m giving two talks. In addition to encryption, I’m talking FTS with Searching Binary Data in SQL Server.

    I’ve given the talk before, and I’m not too worried about it, but I do want to refresh my memory of the flow, and practice the demos again. I have given the Encryption talk a few times this year already, but I was planning on double checking demos again before the event. Especially as I changed the talk around and added some material for a variation I’m giving next week at SQL Intersection.

    I find it’s always good to rehearse my talks. I’m comfortable in front of people, and I know I can get through the talk, but I want things to flow and to make sense to attendees, The more practice I do, the better things go. The less “ums”, “errs” and other placeholders I use as well.

    Plus this will be good practice for SQL Bits, where I’ll deliver this talk again in May.