Friday, February 21, 2020
A link to my complete presentation is here and the toolbox referenced, where you can get those scripts to show off to your friends at parties, is here. If you have any questions, please reach out.
Thursday, February 13, 2020
The slidedeck is available for download here, with many links inside. Any referenced "toolbox" labs are here.
Hey @santafesql! Getting started soon.— William Assaf (@william_a_dba) February 13, 2020
I love this guy's beard on the left.
\/ https://t.co/dj2oYuhWhc pic.twitter.com/ky4AVKDzHJ
Saturday, February 08, 2020
This is an important topic that lives at the crossroads of both of our careers, my wife's career in organizational psychology and human resources, my career in data, and our joint passion for history and civil rights. The effort of researching, paring down, and rehearsing our presentation together as a couple has been an exciting first for us. It's important to understand that when dealing with bias, outcomes matter, intentions don't.
Thanks to the many of you who chimed in during the presentation, including with further reading and book recommendations for us all!
If you'd review any of the topics or case studies we covered, our slides and citations is available for download here.
Thanks to UserGroup.tv, a recording of our presentation is available here.
My wife also presented at Austin SQLSaturday BI 2020 on "Mastering your Resume & Interview: Tips to Get Hired" Saturday afternoon.
Friday, January 24, 2020
Working on a SQL 2017 database where an external, non-Microsoft application has direct access to read/write data via the ODBC Driver 17 for SQL Server.
They suddenly began to experience a regression, UPDATE statements were failing with the following message snippet:
esu_sql_execute (SQLExecute) : [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]
Wednesday, January 22, 2020
|SQL Server 2019 Administration Inside Out|
Technical book writing is such a mixed bag of emotions - long hours writing, existential doubt and validation, progress in seeing chapters move through editing stages, Sisyphean edits, wrangling metadata and chapter status, pride in the finished product, and finally some post-traumatic stress as the next major release of SQL Server approaches. It's been a pleasure to be the ersatz leader of the team, even though I'm not the first name on the book, a lot of work from everyone on the cover goes into producing the content, including our two beloved technical editors Meagan Longoria and Louis Davidson.
So a "fun" look back at our time on the book, spent mostly in Q4'19, seems appropriate as we near publishing.
Similar to our fun author survey from the 2017 book, we the author and tech editor team put answers to questions. This was a nice break while the chapters were progressing through their final edits. The 2019 edition of this book series should be on shelves in Q1'20 and is available for pre-order now everywhere books are sold.
As for this book's fun author survey, I found it interesting how half this team writes with music and half the team must not, how some of us write/edit in odd nooks and some in their home office enclaves, how some of us know how to spend free time and some of us have forgotten how, and how all of us love the new scalar function inlining feature of SQL Server 2019...
1. What music if any did you listen to while writing or editing?
Kudos to Kenny Neal for organizing!
1. The Database Experimentation Assistant uses Distributed Replay to do AB testing for the same workload on different hardware/platforms. Yes, as long as you can connect the application to the SQL Server instance using Windows Auth, you can do AB testing between on-prem or Azure VM instances of SQL Server and Azure SQL Database or Azure SQL Managed Instance, and only between SQL Server on Windows and SQL Server on Linux. More info: https://docs.microsoft.com/en-us/sql/dea/database-experimentation-assistant-overview?view=sql-server-ver15
2. More info on the announcement that you can get SQL Server for free with Software Assurance if it's an Availability Group replica in Azure VM's: https://cloudblogs.microsoft.com/sqlserver/2019/10/30/new-high-availability-and-disaster-recovery-benefits-for-sql-server/
3. Yep, you can put the SSISDB in an Availability Group. You have been able to since 2012, it has gotten easier/better recently. https://docs.microsoft.com/en-us/sql/integration-services/catalog/ssis-catalog?view=sql-server-2017#always-on-for-ssis-catalog-ssisdb
4. Would "OPTIMIZE_FOR_SEQUENTIAL_KEY" help with BULK INSERTS? Parallel bulk inserts maybe. The sequential key hotspot PAGELATCH_EX issue is not I/O related (because it's PAGELATCH_EX, not PAGEIOLATCH_EX), it's memory page related, and it's related to multiple parallel inserts, not just a lot of inserts. More info here: https://support.microsoft.com/en-us/help/4460004/how-to-resolve-last-page-insert-pagelatch-ex-contention-in-sql-server.
5. Parallel Data Warehouse (now inside of the Analytics Platform System appliance) is in a different lifecycle than SQL Server... I'm afraid I don't follow it and I don't know which of these features is getting over into the PDW.
6. There was a question I think about about Resource Governor and Hybrid Buffer Pool or PMEM (Persistent Memory such as Intel Optane DC). I wasn't sure there was a connection at the time. Still pretty sure there isn't. The memory governed by the Resource Governor is not buffer pool memory but query execution grant memory.
7. Accelerated Database Recovery is a SQL Server 2019 feature - it doesn't depend on database compatibility level! Though you do store the ADR version store in the user database (in a filegroup of your choosing), it works with any database compatibility level. More about ADR here: https://docs.microsoft.com/en-us/azure/sql-database/sql-database-accelerated-database-recovery and also in our book, out soon!
8. Are there any drawbacks to enabling the memory-optimized tempdb metadata option? There are some fringe limitations in memory-optimized TempDB metadata that might be an issue for some, but probably not for most. Damir Matešić joined my webinar today and followed up with some more info on the limitations here: https://blog.matesic.info/post/Memory-Optimized-TempDB-Metadata.
If you have any additional questions, feel free to leave a comment here on this blog post or hit me up on twitter @william_A_dba.
Tuesday, January 14, 2020
|Photo: Shaniya W. of The Futures Fund.|
It was great to see so many diverse faces from the Baton Rouge tech scene, including a big presence (and a teenage speaker!) from the Futures Fund!
You can download my slidedeck on Practical Personal Cybersecurity here on my Github.
Thanks again to everyone to was there, and a special thanks to Lynsey Gwin and Quinton Jason Jr for organizing! Please fill out their post-event survey here.
Hilarious and energetic @william_a_dba just gave a great talk on personal cybersecurity at @activ8conf pic.twitter.com/lt1ycqwccp— Christine Assaf (@HRTact) January 15, 2020
"Human in the machine" by @hrtact was a powerful walk through our human responsibilities and needs in technology. Ended with a call for our creativity to enhance, not replace or outdate, real human communication. A strong addition to tonight's @activ8conf lineup of 10 speakers! pic.twitter.com/ng5suJrqTe— William Assaf (@william_a_dba) January 15, 2020