Author: way0utwest

  • Filestream and Filetable in SQL Server

    This talk is an update of my Unstructured Data in SQL Server talk that looks at the Filestream and Filetable features of SQL Server.

    This session begins by presenting a case why we will manage more binary (unstructured data) in the future. The growth of this data is amazing. From there we delve into the basics of the three main types of data:

    • structured
    • semi-structured
    • unstructured

    The session examines the basics of Filestream and how you get enable this feature, administer it from a DBA perspective, and move data in and out of Filestream columns.

    Filetable is introduced along with demos on how to enable this data, as well as a brief search demo to extract information from documents.

    Level: 200

    Length: 60-75 minutes

    Demo Code:

    Slides:

    Related Blogs:

    Presentation Schedule

    This session has been given at these places.

    Apr 9, 2013 – SQL Intersection Spring 2013

  • T-SQL Tuesday #41 – I Love Presenting

    tsqltuesday.jpgThis edition of the T-SQL Tuesday blog party isn’t a technical one. Hosted by Bob Pusateri, this one is timely for me. Bob invites us all to write about how we came to love presentating. That’s good timing as I’m actually giving two sessions at the SQL Intersection conference today.

    T-SQL Tuesday is the monthly blog party, on the second Tuesday of the month. If you’d like to host, contact Adam Machanic(@AdamMachanic).

    I’m Scared

    That’s actually how I felt the first time I had to stand up in front of the class in school and give some sort of report. I can’t tell you when the first time I did it, but I do know that all through high school, and even college, I was scared to be in front of people, palms sweaty, bowels rumbling, and cheeks flushed. I couldn’t imagine voluntarily choosing to stand in front of people and talk about anything. Even talking to a group of 10 people at a party in college made me nervous.

    I Need Money

    College is expensive. When I went through college it was a fraction of the cost today, but it was still expensive. To help out my family, I worked almost full-time to cover my living expenses. The most efficient way to do that was to work in the restaurant business. I learned to cook, clean, and wait on tables. I never had to really speak to a group larger than 8 people, but I was constantly meeting new people and talking to them every night.

    One summer, while home working at a local hotel, our bartender called in sick. I volunteered to jump in, did a good job, and spent the rest of my college career mixing drinks. Around this time the movie Cocktail was released, and many of my fellow workers learned to toss and spin bottles, myself included. It was a little like being on stage in front of groups of people, and over the next few years, much of my shyness in front of strangers disappeared.

    Watch and Learn

    I worked hard early in my technology career to learn as much as possible. I read books, magazines, trade articles, and more, trying to learn as much as I could about the various pieces of technology in my companies. I also attended lots of talks at user groups and MSDN local events. I watched many speakers talk about subjects that I had read about, and worked with myself. I learned lots of things, but more and more I realized that I knew much of what speakers were presenting. I started to think that I could present as well as others. I gained confidence from watching others validate my knowledge.

    Eventually I started SQLServerCentral and there was a year when the founders wanted to do some joint presentations. Brian Knight and I had a debate about identities v GUIDs. It was my first time speaking at the PASS Summit and it wasn’t so bad. We had a lively debate, some input form Microsoft in the audience, and I realized presenting wasn’t so bad. I didn’t jump right in, but a couple years later I was asked to do a short presentation at a local user group and accepted. Fortunately for me this was a small group, and I ended up presenting for 15 minutes while seated a a conference table. Much like being in a corporate meeting, I felt the same mix of nervousness and confidence, but sitting down helped me.

    Over the years I’ve had some good and bad presentations, but I’ve tried to learn from what has worked well and from what other presenters have done. I have written about presenting and tried to help others. These days I’m fairly comfortable talking in front of groups. I know I’ll make mistakes, and that someone in the audience might know more than I do. I know I’ll stumble over sentences. However I move on and don’t worry about those issues. I try to learn from them, but I don’t view them as failures.

    Today I love presenting about various topics. I speak on SQL Server and professional development topics 10-15 times a year. I usually end up giving 25-35 talks, often on 8-10 topics a year. It’s fun, and I really enjoy the chance to teach people something or help them improve their careers.

  • 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.

  • Double Compliance

    hipaa_compliant_seal    vs          pci-seal

    I haven’t ever been bound by HIPAA or PCI regulations with the data I’ve managed. Those laws hadn’t been enacted when I worked in those industries, and so I’ve never had to go through an audit. I have been through ISO 9000 and SOX audits, and I found those audits to be both a pain and also a good idea. Various inconsistencies and exceptions in our policies were found, often strengthening our security or bringing more consistency (and stability) to our organization. Those two audits were also very close in scope and requirements. If we could pass one, we typically could pass the other.

    However PCI and HIPAA are not the same, and you shouldn’t expect that passing one would mean you could pass the other. For most of us, we wouldn’t be bound by both of these, since they are applied to the financial and medical fields respectively. However as we look to move forward and use new partners in business, including cloud services, we should be aware that just because a company has one certification doesn’t mean they have the other. If your business partner is PCI complaint in some way, I wouldn’t assume that this means they are in any way HIPAA compliant, and vice versa.

    Should we have standards for data protection that matter to a variety of industries? I’m not sure we should, despite the hassles that may mean for those of us bound by these regulations. Each industry and type of business has it’s own requirements, some of which are not applicable to other fields. Trying to build one standard for privacy, security, or any other requirement is likely to mean a watered-down, ill-fitting regulation that doesn’t protect any data well. Instead we should have specific requirements we need to meet to provide security (or any other need), without specifics on the technology or implementation used.

    Most of you probably don’t like the idea of any regulation, and I’d like to agree with you. However I’ve seen too many people ignore good practices, engage in morally debatable activities, and in general treat other people, and data, in a way they wouldn’t want to be treated themselves. A little regulation, that limits abuses and gross malpractices is a good thing. Too much regulation, specifying details that are often obsolete before they can be enforced, is a bad idea.

    Steve Jones


    The Voice of the DBA Podcasts

    We publish three versions of the podcast each day for you to enjoy.