If you’re a data professional or application developer chances are you’ve run into Microsoft SQL Server once or twice.
In case you aren’t familiar with #MSIgnite, it’s a huge event where Microsoft debuts all the new shiny software that you’re going to want your hands on immediately and the conference is happening right now and goes until Friday.
You can watch and learn all about the exciting new things at this link:
Hope you enjoy and find some time to check out some of the broadcasting.
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’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’ve been using Microsoft’s cloud database for some time now. I’ve had a few customers with various performance problems and thought I’d take a moment to highlight the interesting behavior you may run into as well.