There is a survey from the WIT group for female speakers. If you are a woman and speak in front of groups, or used to, please fill it out.
This is part of their efforts to help encourage more females to speak and support their efforts. I like the fact that they are reaching out to others to learn how women feel about speaking.
If you know any women that speak, whether in the data community or elsewhere, please pass along the link.
There was a Slack thread at Redgate recently where a developer was showing some code where they decided to use the “extra” column from the information_schema.columns view. They were making decisions on how to detect certain metadata about a column based on the data in this column. Apparently, the data in here is overloaded for different options that might be set on a table.
This caught my eye because I had no idea there was a column named “extra” in this view. I flipped over to SSMS and decided to check what was being stored in here. To my surprise, there was no “extra” column. As I dug in a little deeper in the thread, I realized the developer was talking about Information_schema.columns in a MySQL database.
That was a surprise to me. While I know different platforms will add features and functionality to their databases, I thought the information_schema views were consistent across platforms. They should give you a set of information you can count on. Apparently, that’s not true. You can count on some things, but not all, which means that these aren’t consistent structures.
Perhaps it doesn’t matter. It seems every product out there will extend the SQL “standard” where they see fit, adding features or functions that suit particular use cases. Commercial vendors do this for profit, and OSS projects likely do this because an individual wants a change. That has resulted in a wide variety of database platforms that meet different needs and solve different problems.
It would be nice if we could write SQL code and be sure it would run on SQL Server, Oracle, Snowflake, PostgreSQL, or any platform. And in many cases, we can. Lots of basic queries are the same. However, what would be the point? I certainly don’t want more people in management wanting to switch from one platform to the other, just because they feel like it. I’d imagine that we’d thrash between platforms every time a senior developer or VP decided a system should run on their favorite platform.
A base standard is good, like a base class in programming. However, they aren’t always as useful as they seem, and extending them to meet needs is better for us all. I don’t need a standard implementation of the SQL language or the information_schema views, it was just a surprise to realize that this actually how the platforms are coded.
Note: If you find this interesting, I had a discussion recently with a few others in a webinar.
Steve Jones
Listen to the podcast at Libsyn, Stitcher, Spotify, or iTunes.
You can register today for the 2023 PASS Data Community Summit. This year the event is in Seattle, Nov 14-17, and in-person only. The event was a lot of fun last year, with many great sessions and lots of networking with fellow data professionals.
I’m looking forward to this year’s event. I have submitted a session, though I am hoping for less of a load this year. Last year I had a session, hosted a panel, MC’d two lightning talk hours, was a part of two keynotes, and I’m sure I’m forgetting something. This year I hope to have a few less commitments and see more sessions and friends.
There is a lot to learn, and this is a great chance to talk with many of the SQL Server developers from Microsoft. With the event in Seattle, I expect a lot of them to attend. It’s also the chance to talk to many of the experts in the community. People like Erik Darling, Allan Hirt, Glenn Berry, and more.
This is the cheapest rate you can get now. They’ll be a few price bumps, and there might be some discount codes, but you can register for a three day conference for less now. Talk to your boss, get some funding, make a case for the ROI as well as suggestion that sending you helps retention.
I hope to see you in Seattle this November.
The grade for March is also D. Details below, but just not making a lot of progress in these areas. In fact, I find myself not motivated to work on goals very much. That’s a bit sad, but it’s also where I am in life.
So far I have for 2023:
I set goals at the beginning of the year, and I’m tracking my progress in these updates during 2022.
The last month has been hectic. Both life outside of work and work have had me tackling lots of little tasks, which is distracting and reduces my energy for focused work. As a result, I haven’t been doing much on these goals.
I think I’m slightly overloaded, and worried about burnout, so I’m going to ignore goals for Q2.
Two books on the list: marketing and coaching. I haven’t picked a marketing book, but I picked Wolfpack for coaching. With one started and one not, this is an F.
Progress:
My goals:
Rating: B
I have been tracking my interactions with customers here. There haven’t been a lot, but it is interesting to stop and think about how this is going. I have chatted with my boss and gotten a little feedback.
Here are the goals I set.
Rating: D
I did complete another community (unpaid) speaking engagement. I’ve reached out to a few SQL Saturday groups and we have a few more events on the schedule, but I haven’t had a lot of energy to do this and the limited responses are discouraging.
Yes, I get discouraged.
Haven’t started a tool, didn’t hold office hours, two updates sent.
My goals:
Rating: D
I haven’t updated the Power BI report. In fact, I found a couple errors in calculations since DAX is a weakness of mine. As a result, I pulled down some pages. I also think my data model is slightly broken and needs work. No time spent on here.
It’s been cold, and when it isn’t, I’ve had other things to tackle, so no time on wood projects for me. I feel bad about this, but I also know I have too many hobbies. With my Duolingo language stuff, guitar, and then coaching, not a lot of time to spend here.
Voice of the DBA 