@dataspeakers Could you offer some means to people to filter based on their areas of interest? I can see some new contributors may find it helpful to test the water with pre-recorded, or even blogs, working their way up to full live sessions?
@DataGrillen I had a great day at #datagrillen#dataleftunattended. Thanks to all the organisers, speakers, our sponsor @redgate & most of all to those attending for making it worthwhile.
If you didn't tune in live, I'm told sessions will be on the @DataGrillen channel soon.
I'm looking forward to speaking at @datagrillen's Data Left Unattended #2 conference tomorrow about technology that can help you get your message across effectively - there's still time to join remotely at https://t.co/5hwji5Acpt
@_AlexYates_@redgate I think there's so much domain (business) knowledge required that any tool can only go so far. What would be nice is a framework, and the ability to recognise tags in say, SQL Prompt, highlighting in results and queries like it can production servers now.
@_AlexYates_ don't forget sometimes it is the combination of items that make something sensitive, so a set may only need to be masked if it is problematic as a composite. e.g. age, can be part of an identifier, but not necessarily on its own. Depends on other fields and context.
@_AlexYates_ @stephj_martin @SQLDiplomat @DataMacas@redgate we are putting links to handling instructions from our datasets for this reason. It is useful for (development and) the wider business. Not the same as security permissions. More a case of "Can I vs should I".
@_AlexYates_@DataMacas@redgate also, separate question, should it be unacceptable for masked data (items) to be the same as unmasked ones - or is that only the case for a whole record (multiple fields)? Veering into encryption territory here, but links to unmasking.
@_AlexYates_@DataMacas@redgate yes, I think a flag for whether data has been masked is a different thing to whether it is sensitive. A bit like whether it *should* be accurate vs whether it *is* accurate data... They are two different things. And checked separately.
@_AlexYates_ I work on the assumption that DEV/UAT work will be guided by the classification. So I call that SENSITIVE as the column is designed to hold sensitive data. Also, you fail 'safe' as @BrentO mentioned. We are all fallible; the masking needs good testing too.
@SOZDBA@cl@spaghettidba and the streaming works really well with the provided wireless headphones. Beanbags allow a pleasant and welcome reclined position after a day of using upright chairs in sessions! #SQLBits@SQLBits
@PAH66 did you find a charger? I have a USB C adapter with me (from USB or mains), can loan in the day tomorrow if it helps? (or if you're lodging near the venue, let me know and we can meet up tonight)
@JustSayNoToSpam either here or comments section is fine; it has been a while since I wrote it but the course content is still sound. How have you been getting on with unit testing SQL?