Voice of the DBA

Author: way0utwest

  • The London Redgate Summit Comes on Apr 17

    I’m heading to the UK in a few weeks for the London Redgate Summit. This starts a wild period of travel for me, but I’m excited. This is the second Summit of 4 this year, and it’s a great chance for Redgate customers and prospects to learn about our three pillars of a better database environment:

    • End to End Database DevOps
    • Test Data Management
    • Monitoring

    The schedule is out, with lots of great speakers on a variety of topics. We will have lots of other Redgate engineers and others. I’ve got a few sessions that day:

    • The New Database Landscape
    • Panel: Next-Gen Database DevOps: Introducing Platform Engineering
    • Essential Practices for Seamless Database Deployments
    • Panel: Why the database is increasingly important to the boardroom

    However, there are three tracks running together: New and Future Tech, Deep Dives, and Thought Leadership. Bring a colleague (or two) and attend some different sessions and compare notes during the breaks. We’ve got a lot of info and experts, and this is a great chance to have a team outing. Or maybe a manager/technologist learning day.

    The Redgate Summit is the best chance to interact with the company and learn how we want to partner with you. And that’s what we want to do.

    We’re successful when our customers are successful.

    That’s been an internal theme at the company as we’ve moved to subscription software. We are partners now with all our customers.

    Join me at the the London Redgate Summit for a great time.

  • Off to SQL Saturday Salt Lake City … on Friday

    I’m off on Thursday for Salt Lake City and a SQL Saturday on Friday. SQL Saturday Salt Lake City 2024 is happening, and I’m glad I get to go. I was looking forward to this last year, but it got postponed with venue issues. This year, the timing worked well since I am coaching Sat/Sun/Mon already, so this was an easy trip for me.

    I’ll be presenting my Architecting Zero Downtime Deployments session, looking at splitting up deployments and coordinating with feature flags in your application.

    The schedule has some great sessions. A mix of SQL Server, PostgreSQL, design/modeling, and more.

    If you’re in/near/willing to go to Salt Lake City, come join me Friday, Apr 5. You can register here.

  • CosmosDB APIs Inside SQL Server 2024

    CosmosDB has been a great data platform in the Azure cloud that helps companies deal with disparate types of data. The CosmosDB APIs include those for MongoDB, PostgreSQL, Cassandra, and Gremlin. These wire-level protocols let you work in a way that is compatible with those systems for storing data.

    That’s coming to SQL Server.

    For the last few years the engineers at Microsoft have been working to separate query processing from storage, and they’ve used this to build products like Hyperscale. That work is being added to SQL Server 2024, so that you’ll be able to add a separate storage engine that doesn’t use the same RDBMS/extent/page structure, but instead is optimized to let you store documents, JSON, and other structures. In addition, there will be new query processors that can run queries from your MongoDB, Cassandra, and Gremlin graph clients.

    Like CosmosDB, however, you can’t have relational data and say, MongoDB data in the same database. You’ll need a separate database, and at least initially, you won’t be able to make cross-database queries. However, you will be able to store your relational and NoSQL data inside the same instance. This will make life easier for developers, who will be able to use one server for all their data.

    Of course, this is an April Fools joke and there are no NoSQL enhancements coming to SQL Server. Not for now. I’m not even sure if SQL Server 2024 is a thing.

    Hopefully, you’re dreaming and smiling. Maybe the engineers at Microsoft are as well.

    Steve Jones

    Listen to the podcast at Libsyn, Spotify, or iTunes.

  • Database Mirroring is Back in Azure SQL Database

    Database mirroring was a cool feature in SQL Server 2005. I guess it’s still a feature, though it’s listed as deprecated in the documentation. There is still a mirroring dialog in the SSMS database properties dialog in more recent versions of SQL Server, but I don’t know if there is a good reason to use mirroring over Availability Groups.

    That’s why I was surprised to see a public preview announcement of Azure SQL Database Mirroring to Microsoft Fabric announcement. Apparently you can easily move Azure SQL Database data to Fabric and have it written to Delta Parquet tables in OneLake. No ETL, no need to do the data conversion yourself, or at least not much of an effort. I suspect you still need to understand this and do some configuration for how your Parquet files will get written.

    If you go through the documentation, it’s interesting (and annoying) to me that the docs keep saying replication. I hate when we’ve overloaded terms as mirroring and replication mean specific things in SQL Server, so I wish they would use some other term (copy, extract, ??) to describe what is happening.

    Whether this is useful to analytic workloads remains to be seen. I am curious what the people working with Fabric think of this feature. I wonder if this is useful, or if this might cause headaches or performance issues. Since this feature is in preview, I doubt anyone knows yet, but it will be interesting to see how this compares with Synapse Link and if it is more or less helpful.

    Moving data around for different purposes has always been a challenge. I know that some people might feel the costs involved in this aren’t worth it. I know a lot of technical people that would say “I could do that.” I have no idea what they costs are. but I know that a lot of people have spent a lot of hours managing ETL packages and adjusting them as schemas change and new requirements appear. I get the appeal of Synapse Link and this new Mirroring to Fabric features.

    I do wish this type of feature was more solidly built into the SQL Server instance. I suspect it will come at some point, and it’s being tested and baked in Azure first. However, I hope that if/when it comes, that the feature has good tooling and some polish to its operation. We’ve had too many features in SQL Server that are partially built, with limited tooling, and a lack of performance characteristics that many of us would desire.

    Steve Jones