![]() SQL Server 2022 will be here before you know it. Be sure to check out that video for more details. Once again, this blog just touches on some highlights from Data Exposed. While it’s admittedly something to measure in your own environment, it’s something I look forward to testing for myself to see how it plays out. Depending on the type of XML data pointed to by the data source, you create the dataset query by including an XML Query or an element path. After you define a data source, you create a query for the dataset. I guess we’ll have to weigh those factors to determine if the compression is worth it. In Reporting Services, you can create datasets for XML data sources. We’ll still have the CPU overhead to watch out for. What about helping with I/O performance? With the XML data compressed, that means there’s less data to pull into the buffer pool. Being able to compress some of this data would really help managing disk space. Most will never be referenced again or ever needed. There’s always new XML data coming in and the majority of that data will need be kept for years. I deal with XML almost daily in SQL Server. ![]() The discussion on XML Compression begins at the 9:22 mark. Yes, this is an improvement, but there’s a part of me that hates the idea of someone perceiving this as “great, now I can shrink everything all the time!” I see you scheduling that nightly shrink job. When shrinking databases or files with WAIT_AT_LOW_PRIORITY, new queries requiring locks will not be blocked and will continue to execute. There are also improvements when shrinking databases. Normally qcli and QCTools would store these reports in a gzipped XML file next to the audiovisual film being analysis however, because of the introduction of the Panel features described above, the default. Specifically, concurrent GAM and SGAM updates. To better optimize our workflow, we used our servers to run the QCTools command-line tool (qcli) to generate the QCTools reports at scale. SQL Server 2022 will have some tempdb performance updates which is always nice. Overall, some good info around SQL Server 2022. Other topics include tempdb performance, Shrink DB changes, and more. 4) and one section especially caught my attention: XML compression. I recently checked out the Data Exposed episode SQL Server 2022 Storage Engine Capabilities (Ep. ![]() We’re back to some good old fashioned SQL Server today.
0 Comments
Leave a Reply. |