If you’ve ever been a DBA and seen the mess that you get with SQL Agent Jobs without a clean naming standard for your job schedules and job names then you’ll appreciate this tip.
Azure Purview is a compliance and data governance platform in Microsoft’s Azure cloud. The platform is currently in public preview and has quite a few features; but, does not currently import any of the extended properties that you may have added over the years to your SQL Server objects.
Some time back I wrote about the new data classification features in Azure and SQL Server Management Studio. If you’ve done quite a bit of work classifying your data using the extended properties, guess what?
About a year ago I wrote about a new feature in SSMS that allows you to add a data classification to your columns. Today we’ll discuss what happens behind the scene and how to look at the classifications later.
It always seems that when I give a talk on performance there are 100+ people packed in the room but when it comes to security there’s 10 to 15 people. No one likes patches, unless you’re talking about a puppy named patches or something that’s not related to updates; yet, it’s so important that we all do them.
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.