There is saying “if you want to change some things in your life, you have to change somethings in your life”. So this blog post is part of me changing something in my life. Whilst I might think its a good idea to publicly commit to something then work towards that goal, this is not something that I have done for before. So here goes. Yes this was inspired by the T-SQL Tuesday topic in December 2018, which I mis-read the date for :-)
BIML - this just seems to have so much potential, finding myself writing more and more SSIS packages that have patterns, now's the time to learn more and do more.
My preferred method is video training. This means I am in control of the tempo, if I have 5 mins then can watch a video (or part of). On the other hand if I have not grasped something it is possible to repeat it till I get it. One course on Microsoft Virtual Academy (https://mva.microsoft.com/) about the use of the APPLY keyword I had watch several before grasping the concept. At the moment Udemy is working well for me, just make sure you wait till the one of the regular sales.
In person events is something which has been of massive benefit for me. My first visit to SQL Bits was without doubt a career and life changer. Having the opportunity to hear from so many fantastic amazing speakers is a wonderful. Then there is the networking that is another story, even for a confirmed introvert like me!
Books are still a part of my learning. Recently I have found myself reading more using electronic books. There is difference between a physical book and an electronic book. The later is easier for to take my library with me. So it doesn't matter if the book is at home or work.
Teach - the go to person regarding SQL server in my company is me. At the moment I am writing some lessons to teach what I know about SQL Server and related skills. This encourages me to make sure that anything I am teaching that I have a through understanding of the topic.
Blog - writing posts has been patchy, so this is my commitment to write at least one blog post per month. This year I refuse to allow impostor syndrome to put me off (no excuses).
Submit sessions - on this subject, time to take my own advice / encouragement to speak about what I know, My success is built on those who have taken the time to speak and teach, and I want to give back.
Stack-overflow - having attempted to answer some questions previously with varying degrees of success. Rather than waiting, now the strategy is chasing down questions that I can answer / contribute Who knows chances are that it is myself who will learn more than anyone else :-)
Attend another conference - SQL Bits has been and will be the highlight of my technical year (SQL Geek Christmas / New Year). In 2018 my minimum commitment is to attend at least one other event. If possible as a speaker, volunteer, or at least as an attendee.
Soft skills - ask my partner she will tell you these could do with some work. As a self concession introvert, its not easy to work with people. Recently small achievements mean that it inspires me to learn and work harder.
#SQLGLA 2018 - the Glasgow SQL server user group ran, their first event (2107). This was an amazing learning adventure, so we are getting bigger, watch out Glasgow.
Now that I have committed these goals time to go and start making them happen. Expect a summary in, December 2018.
Forgive me whilst I indulge in some nostalgia first. Whilst at SQL Bits 2016, I finally made the decision to start a SQL user group in Glasgow. If I remember correctly Craig Porteous attend the infamous SQL Bits party and met a gentleman dressed as a Wookie (William Durkin). Now Glasgow has a growing SQL server user group (thanks to a dedicated hard working team). Not only that we just had our second SQL conference! (Yes SQL Bits has lot to answer for ;->)
SQLGLA was a fantastic event it has left me with some wonderful feelings. This blog post is part thank you to those involved, also just to express some of my feelings / experiences of the event.
Craig Porteous, Louise Paterson and I are the people who organised this year's event. I felt we were a team (this is a theme, by the way). Each of us contributed to the success of the event, in a different way. The success of the event was not down a single person in my opinion. It was about us all coming together to make it a success. Craig did put a lot of work into making the event what it was.
There are few words to express my gratitude about our team of volunteers. As an organizing team, we have all volunteered before so we knew what is expected of volunteers. There was a lovely mix of those who have done it before and few who have never done any volunteering. What a team though, they all worked really hard. Speaking personally, I am so proud of them, they made this event for me. Not once did I have to worry about if something was done or not being done. They just made it happen. Whilst I have said this before I cannot thank them enough for being such an amazing team, they exceeded all my expectations.
Last year thanks to William Durkin we had such an amazing lineup, and yet this year lineup was even better! A few days before the event I was looking through the list. It would be a fair comment to say I was blown away by the quality of those who choose to speak at our event. The feedback that I have heard so far the attendees also agree 🙂 Looking the depth of experience and knowledge that was shared, was to me awe inspiring. Whats even better is they all came to Scotland to share their knowledge and expertise with us.
It’s a phrase that I've seen often on social media, these are not just words it's something that can be seen and experienced in real life. To experience it is very humbling and gratifying. A few weeks before the event I was contacted by Chris Taylor (@SQLGeordie) one of the speakers. The speakers had decided they wanted to get something for Craig & Karen Porteous who are expecting their second child. It was my privilege and honor to present the gift on their behalf. Hopefully, Craig will forgive me one day for gate-crashing the closing presentation to present the gift? As Craig knew nothing about this gift.
To make the event something that little different we wanted to find a design for the t-shirts that was rather special. Having worked with Emily Chappell over the years on various projects, her quirky designs and sense of style really works for me. So I suggested we should ask Emily for a design for the t-shirts. The first design was not what we wanted. So next we all got together in a coffee shop at lunchtime. We had a chat did some brainstorming, Emily then sent back a design which we all loved (see picture below). Personally, I’ve never been to a technical conference where they sold the t-shirts :-)
First there are few housekeeping duties to take care, which we are just finishing off just now. Followed by some discussions to see what will be the next step 🙂 All I can safely say is keep looking there will be some exciting news soon....
This post is just some reflections on my experience on speaking, as part of the newcomer track at SQL Grillen 2018
Pre SQL Grillen
This is the first part of this post is written on Tuesday 19th June 2018 only 3 days to go before the session. My current feelings are rather to say the least nervous. Added to that is a considerable feeling of imposter syndrome. At this time my thoughts and feelings are these -:
Rehearsals - without a doubt, going over the presentation multiple times has helped so much more than anticipated. Whilst at this point the words that are going to be used have been repeated many times. They are in my mind. As each slide comes up, there is little doubt in my mind what I'm going to say or how.
Less is more - the amount of material that came out of my research into the topic, not all of it has made it into the presentation. So, what made it in is just what is required to get my point across. Which has upsides and downsides. It should make the session better, more focused, and if people ask questions after the session then other examples and illustrations will spring to mind. On the downside there is part of me that feels like my audience is not getting all that I want to get across. Then again there are only 60 mins which is more than enough for most people.
Imposter Syndrome - not sure what can be said about this. It seems natural, there are many presenters who feel the same. Right now, the best strategy seems to be to focus on the presentation. The goal of the presentation to help one person take one thing away from the session. Who that person is at this moment I do not know. So if just one person takes one thing away that I will count as a win. That person might just be me, which is also good.
Mentor - SQL Grillen, did an awesome job with the new comer's track. Assigning each person, a mentor, for me, I was very luck and have been assigned Cathrine Wilhelmsen as my mentor. Her insights and attention to detail was invaluable in so many ways. Cathrine made excellent suggestions and helped me to see the presentation from the point of view of a non-native English speaker's. Most importantly just generally very encouraging :->
Post SQL Grillen
Phew! OMG! That was soooo scary! Can I try that again?
Back in Sunny Glasgow. Now looking to see what lessons I can learn, and other thoughts spring into my mind.
Bunny in the headlights - It's easy to forget that as a speaker that I felt front and centre. That is to say, everyone can see you and knows you're a speaker, thats how I saw it. Even better or worse, each of the new speakers was given an orange apron to wear. The other speakers had different colours. For me, it was a strange feeling not in a bad way, more that I am usually part of the audience. On reflection its not a bad thing, all part of the learning experience.
Rehearsals – This really worked for me I was able to sit at the speaker's table check my equipment worked, run over my presentation quickly and that was me ready to go. Doing so many rehearsals (and not having any demos) meant for me that I knew what I was going to say and all the notes I needed were on the slide deck. Sitting at the speaker's desk was scary, with so many people who I have seen speak before. At least I was able to make it to a session before I was due to present. Which allowed me to relax and listen to the awesome trio of Rob Sewell (@sqldbawithbeard), Chrissy LeMaire (@cl) and Cláudio Silva (@ClaudioESSilva) talk about the new dbaChecks module.
The Presentation - nervous? YES! Waiting for the session to start was the worst part. Having seen some advice from Brent Ozar I had some music playing (that only I could hear) only thing was I had to resist dancing around. Knowing the presentation allowed me to concentrate on other things.
Audience – making sure I spoke to the whole audience front row to back, both sides, making eye contact with everyone, looking at their body language, to see if my points hit home
Pace - at some points my pace was a little faster than should be, I felt able to vary according to the material and audience reactions.
Body language - both my own to ensure I got points across. More importantly the body language of the audience. Was the audience looking at the slide, or looking at me, did they react how I expected?
The Audience - Think about this afterwards, there were so many more people than I would have even dared hoped for. My guess was about 30 people, some of the people I recognized, my colleagues from Scotland, Craig Porteous, Paul Broadwith, and of course Cathrine :->, and Grant Fritchey aka "The Scary Dba" (yes really!). Somethings seemed to work really well, like the acronyms game, and my alternative job description, yes you had to be there to get the point.
Feedback - for me this was the hardest part. The best that I had expected something like "Meh".
What I did not expect was people saying how well I had done. Grant Fritchey who attended my session, congratulated me on my presentation, even tweeting about as well. Then Alexander Arvidsson also congratulated me on the presentation, his kind and encouraging words can be found in this blog post. Catherine was very generous with her compliments and encouraged me to review the feedback, which was complimentary and insightful.
Finishing - needs more rehearsing, so that the presentation finishes on more of a high, at least from my point of view.
Timing – instead of using a stopwatch, I used a countdown timer. At several points, I was trying to see how much time had elapsed. As my notes had time elapsed at key points. The countdown timer did not make it easier for me to see the time elapsed.
Hard work – Over the years I have been fortunate enough to see many people speak who make it look so easy. Having done it now, its like a swan look they look graceful and elegant as it glides across the water's surface. Yet hidden away underneath the water are the webbed feet working really hard all the time. That’s my experience of presenting, making it look easy requires a lot of hard work, which remains unseen, the way is should be.
Last point is to thank the SQL Grillen team. William Durkin, who does an amazing job of making everyone feel welcome. Ben Weissman for creating and picking the speakers for the newcomers track. There are as l know so many more in the SQL Grillen team, thank you to all.
There are some ideas which are being considered. Where, when and what who knows, watch this space.
Whilst nothing can beat experience having a certificate can also improve the chances when looking for a new job. If an interviewer is looking at two evenly matched candidates, one without a certificate one with a certificate. Personally speaking, if l was the person making the decision then the person with the certificate would the one whom l would recommend getting the job. By studying and passing the exam the candidate has demonstrated, initiative, self-motivation, and a genuine desire for technology. At least that's my opinion. In one case l know of a colleague whom l work with, who said one the reasons they were offered a job was due to the fact that had studied and passed two exams, which were relevant to the role they applied for.
Craig Porteous spoke to some recruiters he knows and asked them some questions about their view of certification. So these thoughts are directly from those who make hiring decisions.
What weight do you put on certifications when hiring?
1) A lot. With two otherwise comparable candidates, the one with certifications wins in my mind.
2) A lot, think it shows that candidates are focused in developing their career.
3) For a technical role I see it as essential
Do you encourage the pursuit of certifications by your team?
Do you see any downsides/negative aspects to certifications?
1) No, none at all.
2) Some of the accreditation's could be more hands on focused.
3) Cost (retaining skilled up workers)
With staff who have completed certifications, do you see any differences in working practice etc to those who haven’t?
1) Yes. People working towards certifications are more engaged with technology and tend to apply their learning in the work environment, sharing their knowledge and improving the overall team dynamic leading to improved productivity.
2) It really depends on the individual so don’t think it’s a fair comparison. Better way to look at it is how doing accreditations adds value to that person in regards technical ability and confidence.
3) Last example was a infrastructure type. Stuck him on a sccm course. A,month later our sccm world upgraded. A year later he left and now heads up sccm at dell secure works in the US . For me a benefit – I get a sccm upgrade from a capable engineer. They get a badge they can use to get their career upgraded. Win win.
One reason l have heard for not doing any certification is the cost. My personal point of view on this is that l am investing in myself. If l learn a new skill gain or learn some new techniques. Yes, the company l am working for will benefit which is excellent news for them. If l choose to move to another role with a different company, then those skills transfer with me. Those skills l have invested both my time and (more importantly very often) my money in they are mine. So my choice is to invest in myself as l believe that the return on investment (ROI) is excellent.
So you have decided to study for certification, what resources are there available? The following list is just suggestions, based on largely on my experience and some others.
If you are planning to take the data platform exams then l would strongly suggest investing in the books for the relevant exam. For example, this one is for the 70-461 exam. The book covers all the topics that could be questioned in the exam. There is an accompanying CD has an electronic copy of the book and practice exam questions. One series of books which I used whilst studying for 70-461 exam Querying Microsoft SQL Server 2012/14 was series titled 2 Joes. The purpose of the books is to take a complete beginner through all the skills required to pass the exam. Personally l found this is the best explanation of how to query xml data using TSQL. They where for me worth the investment.
CBT Nuggets - an excellent resource, the videos l viewed for my 70-462 exam were really helpful. As part of the training package l signed up for included exam questions which l also found where excellent. More expensive that other sites, you have access to all the courses. Really worth considering if want to maximize your study time.
Udemy - with this provider you purchase one course at a time which allows you "lifetime access" to the course. When the courses are on sale, the prices are low. The quality of the courses can vary, so have a look a the reviews on the course before purchasing. Personally, l found the 70-463 covered the basics well, on the other hand, it did not go into sufficient detail for the exam questions.
Pluralsight - this is a well know training site (ok l have heard the name in quite a few place) there are lists of videos for specific certifications. The quaility of the courses l have watched were of a very high quality.
Microsoft Virtual Academy - its Free, which is not always a recommendation. That said the quality of the courses that l have viewed have been excellent. For the exams search for jump start videos, which are a really good jumping off point to start your studying. So excellent hints and tips in the videos from people who passed and training people for the exams.
SQL Bits - apart from being one of the best SQL conferences in Europe. The organizers have given back to the SQL community by recording some of the sessions and making the available for FREE on their website. To find what you are looking for might take a bit of searching, most topics will have at least one video on them.
YouTube - there are a lot of videos uploaded on a wide variety of topics. There will be some searching to find the topic you are looking. On the downside the quality of content is variable. Ranging from the excellent to the not so good.
Blog posts - again this will require some searching. It has in my experience, been worth the time and energy required. One author whilst studying for the 70-463 exam blogged about what she was learning as they went along.
Passing the exams
What is required to pass the exams? Practice and lots of it! One of the keys that are borne out by other people who passed the exams is the practice exams. These exam questions will not be exactly like the exam questions. What they will do is get in the way of thinking when doing the exams. Reading exam questions to see the question, examining multiple choice questions for the correct answer. Best way to get practice is to get hold of practice exam questions and take the exam. There are a number of providers which will allow you to purchase them, MeasureUp, CBTNuggets and others. They will not be exactly the same as the exam questions you take when you go into the exam room. On the other hand they will give you practice at answering the questions. If you pay attention to the score at the end of the practice exam you will also be able to see where you need to improve.
The questions are designed quite deliberately to test your knowledge, well you would not want them to be too easy ? This article from Pluralsight has some excellent examples of the format of the type of question you will be answering in the exam. If you are really interested in how the question are constructed and methodology behind them, this video from Pluralsight has an interview with someone who designs the exams.
All that remains to say if you have decided to study for a certification, good luck and happy studying.
We all communicate with each other, some more than most, in our house if my partner is not talking to me there is something wrong. It's not usual for the misunderstanding to be something I might have said (or done). Communicating with each other verbally is something that we learn to do from an early age. We learn what words mean, their power, what they can do for us, what to say, and what not to say.
There have been times I have had the pleasure of going to the local garage and speaking to the mechanic regarding whatever challenge is with the car. The mechanic would explain the issue to me, using words which I have to say that wished I understood. It is entirely possible that there is a "big end" in our car just do not ask me where it is or what it does. Or that the timing belt is very important to make the engine run properly.
Every industry, profession, hobby, has their own language. This often makes it easy for professionals to communicate with each other often in a form of shorthand which can sound foreign to someone else even if they speak the same language. Working in the IT industry this is something I am very aware of. If someone asks me what I do for a job what do I say? I might say that I am a BI professional, working primarily with the MS SQL server stack, sometimes using SSIS, and SSRS. I write a variety of CRUD scripts in TSQL and I do some query optimisation. If the person asking is not an IT professional who works in my specific area of expertise, most of my explanation would have sounded like I had spoken in a different language.
What I now say is my job involves three things, data shepherding, data grooming, and data dressage. I might expand a little on these to explain that l move data from one place to another ensuring none of the data gets lost as we move it. Some of the data might need to be polished or groomed to fit in its new home. Then I train data to perform and dance in a way that others can understand it better. What I try to do is use words which people who are do not work with databases can understand and relate to.
When I speak to clients one thing I try to remember is to use words that anyone can understand. If I introduce technical concepts or acronyms in the conversation I will try to make time to explain them. Or use analogies that are simple and easy to understand. This is not an easy thing to do, it is our job to make IT simple and easy to use. There might be lots of complicated moving parts behind the scenes. Like a car, we have a simple dashboard, underneath are lots of complicated moving parts that just work. The hard work of maintaining and fixing those parts I happily leave to the experts.
Personally, I see our job is to make our customers task as simple as it can be. We should present challenges, technical details in a language our customers can easily understand. As Einstein is quoted as saying “make everything as simple as possible but no simpler”. One excellent example of this is by Brent Ozar when explaining implications of RTO & RPO here -> https://www.brentozar.com/archive/2014/05/new-high-availability-planning-worksheet/. The worksheet sets out the terms in language everyone can understand, even better by drawing attention to the targets, so everyone knows what to expect.
Is this easy, or simple? No, it is not. Having said that which expert do you feel most comfortable with? would happily go back to time and again? The one that speaks to you in words and terms you can easily understand. Or one that uses language and words that are sometimes not easy to follow or understand? The choice for me is easy and simple, which is why I work that little bit hard to make it as easy as possible for my customers to understand me.
What's so hard about making mistakes for me? The embarrassment of it, maybe I did not know something, or yes that thing that I did well, yes, I did know better. It's not easy for me to admit mistakes. Just ask my long-suffering partner (thank goodness, she does not read my blog!). Yes, I do like to be right and do it the right way. Admitting that I was wrong, or did something stupid, takes it out of me, it's not easy.
Hopefully, in my professional life, I am a little better at dealing with my mistakes. A few years ago, one of my jobs was with a large consultancy company. I was the person responsible for producing reports for the service desk. From time to time there were errors with the reports that I was responsible for producing. During that time, I developed a strategy which I still use to deal with mistakes.
1) Take responsibility
It's not easy to put your hand to say you have made a mistake. On the other hand, how to do you learn from mistakes? For me, part of growing is learning to take the bad with the good. Also personally speaking I have more respect for someone who has what it takes to say when they have made a mistake. Even if you have not made the mistake you find, then take make it your responsibility to fix that mistake. If I do this then my primary focus is to get the issue resolved and move on. Finger pointing or the blaming someone is not part of this.
2) Find the challenge
What when wrong? How did it happen? Be able to explain what happened, in simple non-technical language that anyone can understand. Also be confident that you can explain in technical terms to your peers.
3) Fix it
Get your hands dirty, get involved in fixing the issue. Help find a solution to rectify the challenge or work with the people fixing the challenge if you can. For me, I have and do still learn so much just from fixing mistakes.
4) Prevent it!
Better to have a fence at the cliff edge than a hospital at the bottom. What will stop it happening the mistake happening again? An extra check of something, a checklist of things to do in the same situation.
Is there something I missed, do you have a different strategy. Maybe you disagree? Let me know, every day is school day for me :-)
The core application my current company has built allows people to apply for grants. We track the application through various stages, much like a loan application there are many stages that the application might go through. The status of the application is not linear. So the applications can go back and forth between the same status more than once. In figure 1 below an application .can given a status of ‘under review’ then get a status of ‘submitted’ or ‘Pre-Submission’. So, an application might have the same status more than once with different dates.
Figure 1 –showing the workflow an application might take.
One question which our customers want to know is how long an application takes to move from one status to another. This question could be answered using the existing application database. Using that method is not ideal as the queries are quite complex and slow. This is one of the reasons I decided to build a Datawarehouse as a proof of concept. To see if there was a quicker way to answer that question.
Calculating time difference
Given that an application can be allocated a status more than once during its lifecycle. This has an impact on the method we used for calculating the time difference. The methodology used to get the time difference is defined below
The fact table in the POC Datawarehouse, stores the ApplicationID, Status, and the datetime the application was allocated that status. If an application has been assigned the same status then there would be a record for each time the application has received that status. This has some advantages; the end user can easily understand the data as it is shown in the table. On the other hand, this presented some difficulties with calculating the time period between each status.
After various attempts the following calculated column was created. In this case calculating the days between a grant receiving Pre-Submitted status and Rejected status.
Figure 2 – First version of the calculated column DaysFromSubmittedToRejected
For both values the logic used is very similar, for the variable FirstSubmittedDate the MIN() function is used to get the first date. The FILTER statement only returns records with same ApplicationID and Status = ‘Submitted’. Whereas the variable LastRejectedDate the MAX() function is used to return the last date. Using variables, means the logic can be re-used for other statuses, and the DATEDIFF() function is easier to read. When the results are displayed they were not as expected.
Figure 3 – results from the first version of the DaysFromSubmittedToRejected function see Figure 2
The requirement was to return the number of Days elapsed From Submitted To Rejected with the value returned against the record which is the last time the application received that status. So, another function was created to see if the current record is the LastRejectedDate, which is shown in Figure 4.
With this calculated column (LastRejectedDate) in place the return statement of ‘DaysFromSubmittedToRejected’ function just requires a small change which is as follows
VAR FirstSubmittedDate =
MIN ( 'FactAppStatuses'[DateAddedAt] ),
ALL ( 'FactAppStatuses' ),
'FactAppStatuses'[ApplicationID] = EARLIER ( 'FactAppStatuses'[ApplicationID] )
&& 'FactAppStatuses'[Status] = ‘Submitted’
VAR LastRejectedDate =
MAX ( 'FactAppStatuses'[DateAddedAt] ),
ALL ( 'FactAppStatuses' ),
'FactAppStatuses'[ApplicationID] = EARLIER ( 'FactAppStatuses'[ApplicationID] )
&& 'FactAppStatuses'[Status] = 'Rejected’
'FactGrantStatuses'[LastRejectedDate] = "Y",
DATEDIFF ( FirstSubmittedDate, LastRejectedDate, DAY ),
Figure 5 – Second version of the calculated column DaysFromSubmittedToRejected
When the function is added to the PowerBI report shown in Figure 5 then run then the results can be see in Figure 6 below.
Figure 6 – results from the second version of the DaysFromSubmittedToRejected function (see Figure 5)
The addition of the IF() statement uses the value to check if current row contains the LastRejectedDate. Otherwise it returns a zero. This returns the record set which is expected.
The positive uses of this method are that the same calculation can be re-used for a variety of statuses only requiring a minor change to the formula. On the negative side the more calculated columns there are the longer it would take to generate a report.
No doubt there are other approaches that can be taken to improve this. The time taken to evaluate the calculated column will be slower as the number of rows increases. On the other hand, the current method is significantly faster than doing the same calculations on the application database. Even better with the use of a PowerBI report or a tabular data model. These figures could easily be used by an end user to reports which provide insight into their data. All the better that our clients could do this for themselves, with relative ease.