Business-Intelligence

A current trend that I can’t say that I love is constant churn within software applications. I have no interest to go back to the days where we got a new version of SQL Server or Power BI, etc. every few years. It’s also not a case of who moved my cheese? In fact, I thrive on change. However, I’ve now become really concerned about how anyone: Learns to use a complex application Remembers how to use a complex application when they don’t use it daily I first really struck this issue with Azure.

2018-02-20

In an earlier post, I discussed the design of EAV (Entity Attribute Value) tables, and looked at why they get used. I’d like to spend a few moments now looking at the pros and cons of these designs. Let’s use the same table as the last time as an example: Pros The main positive that’s typically described is that the schema is “flexible”. By this, the developers usually mean “I don’t have to change the database schema (or worse, have someone else change it) when my needs change”.

2018-02-19

I spend a lot of time in large organizations that have spent an absolute fortune on highly-available systems, yet when those systems fail over (just as they were designed to do), most of the applications in the building break. Why? Because the developers have assumed that nothing ever breaks and have written their code in a far too optimistic manner. Did they do their jobs? No Is it possible for their next layer of code to deal with, say, a server disappearing for a few seconds?

2018-02-09

One of the problems with applications that have highly-configurable user interfaces (UI) is that users can end up configuring them in ways they hadn’t intended, and then don’t know how to get back to where they were. I remember the first time that I was at a session with a presenter from Microsoft showing the (at the time) new personalization options in ASP.NET. You could build a website and let the user determine how the site should be laid out, to suit themselves.

2018-02-08

One of the endless challenges when working with databases (and not just SQL Server databases) is processing dates and times. While there are some good date-handling functions in the T-SQL language, there are many more gaps in what’s offered. This month, we’ve filled another one of those gaps. In Australia, whether staff are religious or not, the Christian Easter is associated with a four-day weekend for most workers except those in retail ie: Friday (Good Friday), Saturday (Holy Saturday), Sunday (Easter Sunday), and Monday (Easter Monday).

2018-02-07

Digital Transformation and Cloud Transformation are phrases that I hear bandied around at nearly every large organization that I currently doing consulting work for. Yet, in so many cases, I can’t see the organization achieving the changes required. This is for two core reasons: The first is that the culture within the organizations is a major hurdle. There just isn’t enough flexibility to think outside the box about alternative ways to work.

2018-02-06

One question that I’m asked all the time when consulting is whether reducing the size of database tables will make queries run faster or not. The underlying question is typically about whether the client should implement some sort of archiving strategy, to reduce the amount of data in a table by moving older data off into another table. My answer is that it might help, but if it does, you probably have another issue that would be a better one to solve instead.

2018-02-05

SQL Server Management Studio (SSMS) is a great tool and it has lots of helpful menu items and toolbar items. Unfortunately, all these items take up screen real estate. You can see that the default screen layout could be considered a bit cluttered if you really just want to focus on the particular query that you’re working on. A keyboard shortcut can help here. Alt-Shift-Enter toggles full screen mode in SSMS.

2018-02-01

When many SQL Server customers are asked why they haven’t kept up to date with either SQL Server versions, or more importantly, patches to SQL Server, the answers usually boil down to two reasons: They are just slack Their vendors won’t support the later version or patch level Many SQL Server application vendors don’t keep up to date with testing of their applications on released versions or patches for SQL Server.

2018-01-30

I keep doing work at sites where none of the database code is stored in version control (source control) systems. I keep wondering why that is. At a recent site, all the source code was in individual files just sitting in a single folder. That’s just not sensible. I’m left wondering why it is that almost every team that I see working with higher-level languages just assumes that some form of source control would be used, yet it’s almost the opposite when I’m working with data teams.

2018-01-26