SQL is a stout language and SQL Server has so many features that it’s impossible to be an expert in everything. I see a lot of people gravitate towards performance; but, that’s not the best place to focus. If you don’t know the fundamentals of the language then you will never be the best performance tuner.Read More »
Understanding the fundamentals is key for success, with everything you do. These days SQL Server has expanded into much more than just a database; but, products that ingest data for analysis still need to get the data from a source, such as an OLTP SQL database.Read More »
I’ve been in technology a long, long time (more than 2 decades). Over the years, I learned Access which took me to Oracle and then translated nicely to SQL Server where I’ve spent the bulk of my time.
Along the way different projects had different requirements and challenges. To take these on and be a better DBA, I learned VB 6 and then VB.NET. A C++/C# developer asked why I was wasting my time relearning VB when I could learn a real language (C#). Years later I got tired of TechNet samples being only C# and I learned it and primarily use C# as my dev language of choice today.
It’s Friday and I’m ready for the weekend as I’m sure everyone else is. This weekend I’m looking forward to getting yard work done and browsing through the whoisactive SQL Ops Studio extension code.
Many of the widely advertised and talked about features of SQL Server or other software products focus exclusively on the hip new thing as opposed to quality of life. I’ve even recently heard people complain to Microsoft that they only focus on new features instead of making existing ones better.
I last posted about changing a table without changing a view that represents the table and how this may affect the view.
In today’s quick post I’d like to show another issue brought about by not maintaining your views.
I had a fairly puzzling issue today, which took a few minutes to figure out. Some time ago I created a “history” table. This was before temporal tables came out in SQL.
Databases are platforms that are designed to securely store and retrieve your data. Perhaps that’s why they’re called a data “base”? So if your data is in a base, you’d want to lay it out in some logic way.