I will be attending DellWorld 2016 as an influencer/media/analyst participant. This means that I’ll get access to the regular sessions, plus special engagements with product teams to see what they’ve been working on recently and what they want to do in the future. I’ve attended a couple of Dell on-site events and am looking forward to talking to key customers and real-world, hands-on data professionals. Also, doesn’t everyone want to visit Austin as much as possible?
If you will be attending Dell World, let me know. I hope we can #selfie. Or just have a real conversation. Or we can get breakfast tacos.
I’ve been extremely lucky to have my sessions selected for speaking at PASS Summits for 4 of the last 5 years. One year all my topics (data modeling and database design) were deemed to be “off-topic” for the Summit crowd. The good news I still got to speak because each of the two founding organizations (Microsoft and CA) let me use one of their slots or co-presented with me on the topics of database architectures and designs.
One of the outcomes of speakers using their community slots to do sales from the podium is that this event now has a rule that your slide deck can have only one mention of your name and our company. Yes, because people were being overly focused on what they could get out of the crowd instead of sharing knowledge with attendees, the rest of the speakers and attendees have to feel pain.
I’m proposing that we allow speakers to put a form of their About Me slide at both the beginning and the end of a slide deck. Yup. Just one more slide.
The first About Me slide is to establish a the speaker’s credibility on the subject, plus to disclose any potential conflicts of interest the speaker might have. Speaker works for a vendor? Check. Speaker wrote a book on this? Check. Speaker is a data architect and not a DBA? Check.
Note that having a potential conflict of interest on a topic isn’t necessarily a bad thing. It’s just a disclosure, not a confession. In the past, when InfoAdvisors partnered with vendors, that would be on my About Me slide for presentations about data modeling, because I had partner agreements with most of the data modeling tool vendors. We don’t have partner agreement any longer, but we do work with data modeling tool vendors.
When I speak in vendor-hosted slots, I’m careful to explain to attendees that they are in a paid speaking session and I disclose why I’m there and whether or not I was compensated to be there. In the Summit year I spoke in vendor slots, I wasn’t compensated other than to get a spot via means other than the program committee.
The second About Me slide, at the end of the deck, plays the role of "Okay, I just talked with you for an hour about something I’m passionate about. If you’d like to talk more about it, or if you have problems with my demos, or if you have a question you want to ask me, here’s how to reach me.
For me, this isn’t just the norm for all events, it’s etiquette as well.
Some speakers in the community have said “but all the attendees know who we are”. No, no they don’t. Celebrity is a bit overrated here.
Regulation is Born from Bad Behaviours
I think it’s odd our community has a rule that keeps us from doing the second slide. I know the rule came from speakers who were overly sales-y in their talks. That’s what makes me sad about the other discussions I blogged about yesterday. Bad behaviour by sales-focused speakers ruins the experience for attendees at the event and for years after.
Bad behaviour by sales-focused speakers ruins the experience for attendees at the event and for years after.
If we started collecting data from attendees about how promotional speakers were in their sessions, that would be a much better indicator of whether or not sales was happening from the podium. At EDW for the last several years, the attendee survey asks people:
“Was the speaker too "commercial?" i.e. did he/she seem to be selling their own product / services / book / etc.?”
It’s a simple Yes/No question. The measure is reported back to the speaker and the event organizers. The overall conference evaluation asks for the attendees to list the speakers who were overly sales focused during the event. I think that’s a great question to ask the community. This data is much more likely than the ban on mentioning your name more than once in an hour to indicate whether or not the speaker is there to sell you his or her stuff.
One of the reasons decks have to be submitted for review at Summit is so that dozens of volunteers can scour the slides for mentions of the speaker’s name or company. That isn’t really a value add for attendees, yet we do it because people have been overly focused on selling their products or services instead of the community. We’ve incurred a huge cost (in volunteer hours) to enforce this and some other less important things AND added months to gap between slide preparations and presentation time. This leads to pain for both the speakers and the audience.
Speakers break this rule all the time. Some get called out, some don’t. We basically have a rule that is unevenly enforced and silly. It’s time to change this rule.
It has been five years I’ve been asking for our community to change this rule. I believe I’ve followed it every time I’ve presented at Summit. There may be a time when the last slide from having given the presentation before has stayed in the deck, but I really want to follow the rules. So now after 5 years of emails and chats, I’ve blogged about my idea for win-win solution in hopes that other community folks will say “yes, I think that’s a good idea”.
Make it Right
We should be asking attendees of sessions and in the overall conference evaluation if a speaker spent too much time selling his blog, his books, his services or his products. We should allow two slides about the speaker in a slide deck. These two changes to our rules will benefit attendees and speakers. These changes are win-win.
There have been some blog posts floating around about a new PASS Summit policy. Most of the posts have been either misleading or ill-informed about why this new rule came about. Last year there was a sh*tshow of bad marketing and sales practices:
- Two vendors did a bulk drop of branded promotional items in the Community Zone. They literally turned an area intended to be about chapters, networking, and #SQLFamily into a their own company litter box.
- A vendor lefts stacks of promotional items on booths of sponsors in the exhibit areas. Yes, a vendor who did not pay to sponsor the event used the booths that other vendors paid for to attempt to distribute their marketing materials.
- I heard of other things happening from sponsors, but did not witness them. They were right along the lines of those two things above.
So PASS has come out with a new rule about exchanging stuff at the PASS Summit. They are now going to attempt to limit exchanges to business cards only. I think this is way too specific of a rule definition, but unlike the other bloggers, instead of making this a post about how awful the board is, I’m going to offer up win-win-win alternatives below.
Some of the comments on these posts have been made in an attempt to soften the “guerrilla marketing” bad behaviours I mentioned. They claim that the board wants to limit small, personal exchanges of gifts like ribbons and stickers, both very common conference exchanges. In the space community, these also include mission patches and pins. I don’t believe the board wants that, but they have certainly put that in writing.
First, the rule right now only applies to speakers. I’m not sure if it applies to attendees, but I’d want any such rules to apply to everyone at the event.
Feral Cats and What’s That Smell?
The issue isn’t about personal exchanges of gifts. The issue, as all of us know here but are pretending we don’t, is the literal carpet bombing of commercial collateral, including promotional, branded swag in community areas, empty session rooms, empty tables, restrooms, hallways, charging areas, etc. I do not support the claims that this type of feral-cat like spraying of vendor materials is “Community over Sponsors” behaviours. It’s about sales over members. Don’t kid yourself. Consultants are vendors. InfoAdvisors is a vendor. I’m a vendor at these events because I work for a vendor.
Consultants are vendors. InfoAdvisors is a vendor. I’m a vendor at these events because I work for a vendor.
All that spraying smells. It’s only community if your business belongs in a back alley. It’s only community if you think of attendees as “prospective invoices”. It’s all litter box marketing.
That isn’t about gifts. It’s not about community.
And what has happened is that the “arms race” mentioned in one post has now become such an embarrassment to the community that our professional association has had to step in and make a rule.
Update: One vendors claims that the sponsors asked him to drop swag on their tables. “it just looks like litter boxing” (paraphrased). The two events I witnessed involved the sponsors throwing the swag in the garbage and asking “WTH was that?” I’m going to guess that “being invited to give out swag at the booths” is a giant misunderstanding. Ha ha. : ).
The New Rule Isn’t Right
I agree that the limiting to business cards is a unacceptable way to draw the line on this “I don’t see you all as community but as potential invoices” behaviours. But the real fault is on the people who need to have the event as a “sell-first, avoid you later” event.
Saying they can’t afford to have a booth isn’t accurate. It’s affordable. Many smaller vendors have booths at SQL Saturdays and at the big show. It’s very affordable, especially if you share with other vendors. Which is a great way to have a booth because who wants to man/woman/kitten a booth for the entire conference?
Should you have to have a booth to exchange stickers or ribbons? No. But when sponsors get other people’s swag dropped on their booths, or when the community zone becomes a porta-potty for marketing materials, we’ve lost our path. No matter what someone tells you, that’s not community. It’s seeing our event not as a Connect. Share. Learn. event. It’s about seeing our event as a Speak and Sell event.
Blame for the new rule goes 100% to the folks who did these things. Okay, maybe I’ll blame the board 10% for coming with a new rule that isn’t quite a win-win-win solution.
This Ain’t the Tea Party
If you think telling sponsors “we’ll take your money, but others can turn the community zone into their own “rogue exhibit hall” is good conferences sales point, I suggest we just give away exhibit booths and charge everyone the real price it costs to put this on. I’m guessing that registration will cost about the same as a 7-day cruise. Or it will be like a local user group meeting, with fewer people. Austerity might be your political stance. Telling people to just change jobs if their employer won’t pay $7k for them to attend Summit is a nonstarter.
The fact of the matter is that community events the size of Summit (thousands) can’t happen without sponsors. Ensuring that sponsors get what they pay for is not “putting sponsors over the needs of attendees”. It’s about running an event that is affordable and sustainable. Sure, it’s a balance. But pretending that somehow non-sponsoring vendors should be allowed to use sponsor resources for their own needs is naïve at best. At worst, it’s painting the situation as being something it is not.
Data. Get Your Data Right.
It’s misleading to say that these rules happened because PASS wants to cater to sponsors over community. A few overly-greedy, it’s-all-about-money people have caused this. Focus your ammo on the right malicious “users” of PASS.
What I Want the Rule to Be
I’ve talked to board members and PASS staff. This is what I want the rule to be. I think it’s a win-win-win for attendees, consultant and sponsors.
Personal, one-on-one exchanges of low-cost items like the ones below should be allowed and even encouraged.
I don’t care if those things have your name, your favourite tagline, your picture, your cat-owner’s photo, or your logo. They key here is one-on-one, personal exchanges of low-value, often fun, things. I also don’t want to have a detailed list. People love to have a check box set of rules, but that just leads to people finding loopholes. Heck, I love sharing space swag at non-space events. Especially collectibles that are older than most of the attendees.
Update: What do I mean by exchanges? I mean giving out these low-cost items in trade for the other person’s similar item or for some other value. One year at EDW I asked people to tell me they “loved their data” to get a ribbon. Hearing people say that was a small but important value to me. I may have done that at Summit one year as well. The key is these are still one-on-one exchanges. And none of them happened from the podium. Selling while presenting should be a paid session.
Ribbons, stickers, stamps are all part of the geek community and I want that to continue to be a part of Summit.
Bulk distributions of marketing materials, flyers, branded materials should require some sort of sponsorship level. As should the distribution of more expensive swag, cars, real tattoos, kittens, and $20 bills.
Distribution of items on sponsor booths without their permission should not be allowed. Bulk distribution on the exhibit floor without being a sponsor or in the Community Zone should not be allowed.
The Community Zone Should Be a Sales-free Zone
The Community Zone should be sales-free, as far as I’m concerned. It’s the violation of this rule that I think should cause people not to be invited back to the event. Attendees should have one area where they aren’t treated like invoices. Having to put this into a rule makes me sad. People should just understand this is how life works.
Maybe we need a $500 sponsorship level for those vendors whose business is doing so poorly they can’t afford a booth. Or for independent consultants. Again, this is for people and organizations that want to do mass distribution of marketing materials and collateral, not personal exchanges.
A professional association should indeed help all members be great at what they do. Whether they are consultants, software vendors, contractors, full- or part-time employees, retired, whatever. But that doesn’t mean that a professional association event must provide a sales opportunity in every part of the event.
This proposal is a win-win-win because attendees can keep doing what we’ve always done. Vendors can still do their sales things, but appropriately. Vendor sponsors can keep getting value out of their sponsorship dollars without some on other vendor being a feral cat and bragging how “sponsoring a booth is stupid when you can just do guerrilla marketing.” Our sponsors are part of our community, too. In fact, organizations can be members of PASS if the sign up.
The world does have bigger problems. But the posts that have been coming out have not been giving the full picture, nor have they offered up a balanced solution. I think it’s good that this year several people came forward to complain to the board that the stuff people have been doing has crossed a line. It may not really be an “arms race”. But is has been escalating. Houston, we’ve had a problem. It stinks. It’s time to fix it. Let’s all work together to get it right, before the urine smell kills the whole event. If you have other ideas, I’d love to hear them.
This is some of the feedback I got for speaking up.
I’ve never attended a SQL Saturday Ottawa yet (there’s always been a scheduling conflict). I was not in Ottawa that day. I was at a NASA Armstrong Teacher Educator event.
This is how nasty this whole discussion as become. A vendor took a bunch of my tweets over the last year, some about these behaviours, some about my dislike of the things that Mr. Trump says, and some about God knows what else and made a video saying I’m mean. Then this video became a facebook post on the vendor’s own Facebook wall.
A few people spoke up and this commenter deleted his comment after a while. The vendor did not delete it. The commenter did. Remember this when you are thinking about win-win-win solutions. This is what’s at stake. This why bad behaviour leads to more bad behaviour. I’ll still keep blogging about it. And people will still comment on ME instead of the issue.Its what is broken with our community. Talk about bad behaviours, not people.
I’m visiting Dallas this week to speak at the North Texas SQL Server User Group this Thursday. I’ll be speaking about keys: primary keys, surrogate keys, clustered keys, GUIDs, SEQUENCEs, alternate keys…well, there’s a lot to cover about such a simple topic. The reason I put this presentation together is I see a lot of confusion about these topics. Some of it’s about terminology (“I can’t find anything about alternate keys in SQL Server…what the heck is that, anyway”), some of it is misunderstandings (“what do you mean IDENTITIES aren’t unique! of course they are…they are primary keys!”), some of it is just new (“Why the heck would anyone want to use a SEQUENCE?”).
We’ll be chatting about all these questions and more on Thursday, 17 March at the Microsoft venue in Irving, Texas starting at 6PM.
Attendance is free, but you need to register at http://northtexas.sqlpass.org/ to help organizers plan for the event.
Don’t worry if you don’t know about SQL Server or don’t use it: this presentation will focus on some SQL Server specific features, but the discussion is completely portable to other DBMSs.
So many of us have learned database design approaches from working with one database or data technology. We may have used only one data modeling or development tool. That means our vocabularies around identifiers and keys tend to be product specific. Do you know the difference between a unique index and a unique key? What about the difference between RI, FK and AK? These concepts span data activities and it’s important that your team understand each other and where they, their tools and approaches need to support these features. We’ll look at the generic and proprietary terms for these concepts, as well as where they fit in the database design process. We’ll also look at implementation options in SQL Server and other DBMSs.
Hope to see you there!
It’s a new year and I’ve given Thomas LaRock (@@sqlrockstar | blog ) a few months to recover and ramp up his training since our last Throwdown. The trophies from all my wins are really cluttering my office and I feel back that Tom has not yet had a chance to claim victory. So we will battling again in just a few days.
I’ll be dishing out the knowledge along with a handkerchief for Tom to wipe up his tears at SQL Saturday #461 Austin, TX on 30 January 2016. This full day community-driven event features real database professionals giving free presentations on SQL Server and Data Platform topics. All you need to do is register (again, it’s free) before all the tickets are gone.
Database Design Throwdown
Duration: 60 minutes
Track: Application & Database Development
Everyone agrees that great database performance starts with a great database design. Unfortunately, not everyone agrees which design options are best. Data architects and DBAs have debated database design best practices for decades. Systems built to handle current workloads are unable to maintain performance as workloads increase.Attend this new and improved session and join the debate about the pros and cons of database design decisions. This debate includes topics such as logical design, data types, primary keys, indexes, refactoring, code-first generators, and even the cloud. Learn about the contentious issues that most affect your end users and how to avoid them.
One of the other great benefits of attending these events is that you get to network with other data professionals who are working on project just like yours…or ones you will likely work on at some point.
Join us an other data pros to talk about data, databases and projects. And make sure you give a #datahug to Tom after the Throwdown. He’s gonna need it.
On 12 April 2011 it was Yuri’s Night — the night we space fans celebrate Yuri Gagarin’s 1961 history-setting flight into space. In 2011 we were celebrating 50 years of manned spaceflight. On that same day in 2011, we reached the end of support for SQL Server 2005 SP4. On 12 April 2016 we will reach the end of extended support for SQL Server 2005. That means no more hotfixes, no help from Microsoft and no love for your data still living in SQL 2005 databases.
I’m hoping your organization is already on its way to upgrading and migrating data and applications to newer versions of SQL Server. SQL Server 2016 is already being used in production by early access customers. No matter which version you will be migrating to, I want to share with you some of the features and perks you’ll have available to you now that you are moving away from a dead version. Of course there are hundreds of enhancements that have happened since 2005, but today I’m focusing on those that a data architect would want to use in a database design for enhanced performance, security and data quality.
If you are designing for data warehouse type solutions, this is the closest thing we have for a "turbo switch" for SQL Server. Columnstore Indexes achieve high compression rates since they store columns together instead of storing rows together. They also support much faster query performance for batch and aggregation queries. They typically achieve 10x performance increases, sometimes even more. This feature was introduced in SQL Server 2012, but you’ll want the advances to this feature that came with SQL Server 2014.
SEQUENCEs have been around in other DBMSs for a while, but were introduced in SQL Server 2012. These special objects work much like IDENTITY columns, but offer more flexibility and use cases. The main feature is that you can grab a sequence (or a bunch of them) before you insert a row. Many developers use GUIDs for similar reasons, but GUIDs are much longer and therefore had performance downsides. SEQUENCEs are integer types.
New Data Types
So many new data types have been introduced since SQL Server 2005, but the ones that really stand out for me are DATE, TIME, DATETIMEOFFSET, the geospatial types, and the deprecation of timestamp.
It wasn’t until SQL Server 2008 that we had access to data types that comprised only the DATE or TIME portion of a point in time. So we had to do all kinds of conversions just to strip out unwanted data (00:00:00). We also had to make room to store that unwanted precision. Storing millions of rows of unneeded zeros hurts performance, both operationally and for backup and recovery.
SQL Server 2008 also introduced DATETIMEOFFSET, which allows us to track data in context of its time zone. If you remember the days when meeting invites did not include this important piece of information, you’ll know why this is important.
The spatial data types GEOGRAPHY and GEOMETRY and have added a new and feature-rich way of tracking places, their geometry plus special features that make it much easier to answer questions like "which is the closest" or "is this address located in this neighbourhood". If your data story includes location points, you’ll want to use these.
SQL Server was always an oddball when it came to the data type TIMESTAMP. In other DBMSs, this data type was one that included date and time, to a very large precision. In SQL Server, TIMESTAMP is a type of row version identifier that has nothing to do with TIME. So data architects migrating from other DBMSs were often bitten when they used the wrong data type. Microsoft announced in 2008 that it was depreciating TIMESTAMP and recommending the use of ROWVERSION, which is similar (but not the same) in functionality.
SQL Server 2016 currently includes support of Always Encrypted, a feature that does just that: it support the encryption of data from application to database and back, so that it is better protected than solutions that encrypt data once it is written to the database. I’m always reminding you that keeping your CIO out of jail is part of your job description, right?
As our data gets bigger and bigger, the size of our databases is growing as well. That means that performance takes a hit. Developers want us to take shortcuts on data quality to improve performance because size matters. One of the ways to help manage data volumes is to move "cold" data to other storage locations. Starting in SQL Server 2016, we can stretch a database to Azure, which means that data that isn’t accessed as often can be stored in the cloud and retrieved when needed. This allows our hot data to be local and fast, while the cooler data is more economical to store and still there and your application doesn’t even have to manage this difference.
In SQL Server 2016 we are getting support for JSON processing. This isn’t the same as a JSON data type like we have with XML, but a set of import and export features for providing relational data as JSON documents and brining JSON data into SQL Server. Now you won’t have to manage all those curly brackets on your own.
One Last Thing…
As vendors withdraw support for their products, third party tool makers do so as well. If you are supporting older, out of support versions of databases, it’s likely that your data modeling, data quality and data integration tools are also dropping support for these solutions. You’ll be left supporting database systems without vendor support and without professional enterprise class modeling and design tools. I know how hard it is to keep track of databases that my tools can’t connect with. Don’t let sticking with an old version be the end of data modeling support for that data.
If you like geeking out about space and data types, you might want to check out my 1 April 2014 post on a new data type.
Show Your Data Some Love
These are just a tiny number of the types of features that will be available to you when you upgrade to modern versions of SQL Server. The advent of security, data quality and performance features are leaving your old solutions behind, putting your data at risk and leaving your customer data feeling unloved. There’s a data space race going on. Don’t live your company using old technology to manage data. Go fix that!
I’m excited to announce that Thomas LaRock (@sqlrockstar | blog) and I will be presenting a full-day Training Day (PreCon) at SQLBIts XIV in London, UK.
Our session, Designing For Performance: Myths and Misunderstandings, is going to feature hands-on labs, exercises and lots of challenges to help you master your own SQL Server superpowers. It will be held on Thursday, 5 March 2015. Registration is open NOW.
Everyone agrees that great database performance starts with great database design. So why do so many poorly designed databases exist in the world? Attend this session to understand why bad designs will always exist, what you can do to avoid them, and how best to work with them when needed.
Discussion topics will include:
- Server/Infrastructure design
- VM/Server configuration
- Physical file layouts
- HA/DR options
- Database/Table design
- Table design
- PK/FK choices
- Index strategies
- Monitoring for performance
- Control reports
Attendees will leave this session with an understanding of the following:
- Why common issues are so common
- How to better anticipate issues before they happen
- How to deploy and implement design choices that benefit everyone
- Proper performance benchmarking and control reports
This will be my 3rd SQLBits conference, They are a lot of fun and jam-packed full of learning and networking. As you can see from the video above, Tom and I will also ensure that you aren’t just sitting through 8 hours of bullet points and sparse slides with funny pictures. We’ll be talking about what design approaches work in what situations and all the myths and misunderstandings out there about database design and configurations.
Register now and engage your own superpowers. Or just stand there looking pretty. It’s up to you.
Subscribe via E-mail
- September 2016
- August 2016
- June 2016
- May 2016
- April 2016
- March 2016
- February 2016
- January 2016
- December 2015
- November 2015
- September 2015
- July 2015
- June 2015
- May 2015
- April 2015
- March 2015
- February 2015
- January 2015
- December 2014
- November 2014
- October 2014
- August 2014
- July 2014
- June 2014
- May 2014
- April 2014
- March 2014
- February 2014
- January 2014
- December 2013
- November 2013
- October 2013
- September 2013
- August 2013
- July 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- September 2010
- August 2010
- July 2010
- February 2009