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.
If you’re in Chicago on March 17 and have some free time, why not check out all the cool kids?
One of the things I enjoy most is diagnosing storage latency. I honestly couldn’t tell you why I enjoy it so much; but, I just do. When it comes to storage in Windows one of the best things you can do is capture an ETL trace for the STORPORT driver.
I’ve never been a fan of a GUI for DBA work. Give me a hand crafted script or a list of DMVs and I’m a happy camper.
Perfmon is probably my best friend. It’s always there and happy to tell me the truth. It seldom falters and has helped me get to root cause on even the toughest of performance issue. But what about PaaS?
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.