The missing index DMVs are great but they’ve always been missing something.
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.
Security is an important and often overlooked function of technology. Don’t believe me? Go to a SQL conference and look how many people are listening to the perf tuning session vs the 3 people attending the security session.
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.
Azure SQL DB is a robust data platform that’s cloud native and can be managed from SQL Server Management Studio (SSMS); though, the management tasks available from SSMS for Azure SQL DB may not exist, such as: data classification.
The right to be forgotten. It’s a concept that sounds great for people who are concerned about their personal information (PII) but it’s a complex issue for developers and data professionals.
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.