A Fine Slice Of SQL Server
Well…..I just learned about these and thought that it would be good to understand them a little more and have some links to read more about them. I honestly don’t have a lot of SQL 2022 servers in our customers SQL estate, so this has flown under the radar for me. This will be an attempt to put some spread-out information in a one-stop shop.
Click through for a table with information on roles, as well as lists for permissions.
Comments closedReitse Eskens shares some thoughts:
It’s been a long time coming, but all of a sudden there were a number of posts from Microsoft announcing the first preview of SQL Server Management Studio 21. This is big as it’s quite the overhaul from the SQL Server Management Studio we’re used to.
To give you some idea, here are my first impressions.
Vlad Drumea also takes a peek:
SQL Server Management Studio 21 Preview 1 was released 2 days ago, so I took it out for a spin and here are my first impressions so far.
Read on to see what’s in the preview today, some of the new functionality, and whether SSMS 21 is faster than SSMS 20.
2 CommentsColin McCabe announces Apache Kafka 3.9:
We are proud to announce the release of Apache Kafka 3.9.0. This is a major release, the final one in the 3.x line. This will also be the final major release to feature the deprecated Apache ZooKeeper® mode. Starting in 4.0 and later, Kafka will always run without ZooKeeper.
That’s a pretty big change, but there are also quite a few other significant changes here to check out.
Comments closedAjay Jajoo tells us what’s new:
One of the standout features of .NET 9 is its focus on performance. With numerous optimizations across the runtime and libraries, applications can expect faster execution times and reduced memory usage. This is particularly beneficial for high-load applications, making .NET 9 an ideal choice for cloud-based solutions.
.NET 9 brings various performance optimizations, including improvements in garbage collection and just-in-time (JIT) compilation.
If you work at all with C#, you’ll see some quality of life improvements in .NET 9. But given Microsoft’s policy around short-term and long-term releases, you might wait until .NET 10 in many corporate environments to see them.
Comments closedJosephine Bush performs a migration:
Why Migrate to Flexible Server?
- High availability and disaster recovery: Flexible Server provides higher availability with zone-redundant architecture.
- Customizable maintenance windows: More control over when updates and maintenance tasks occur.
- Performance improvements: Fine-tuned scaling and performance adjustments without downtime.
- Enhanced security: With VNet integration and more advanced networking options.
Read on to learn more about by when you have to migrate and how you can perform the migration.
Comments closedDjordje Jeremic announces general availability of one of the key selling points from SQL Server 2022:
Today, we are announcing the general availability of the following two major capabilities of the Managed Instance link feature with SQL Server 2022:
- Two-way failover between SQL Server 2022 and SQL Managed Instance through the link to unlock true disaster recovery (DR) with Azure
- Creating a link from SQL Managed Instance to SQL Server 2022 to unlock off-PaaS data mobility for regulatory and dev/test scenarios
Click through for more detail.
Comments closedBrent Ozar reminds us that small changes happen:
About 10 years ago, Microsoft made changes to the Cardinality Estimator (CE) which caused some problems for SQL Server upgrades. When folks upgraded to SQL Server 2014, they also casually switched their databases’ compatibility level to the latest version, because for years that hadn’t really affected query plans. They just figured they wanted the “latest and greatest” compat level, without regard to the effects. That backfired badly when they suddenly got 2014’s Cardinality Estimation changes.
So for several years, whenever someone upgraded from older versions, and they complained about performance, the stock community answer was, “Change your compatibility level back to what it used to be.” In many cases, that just solved the problems outright, leading to blog posts like this and this.
Even today on SQL Server 2019 & 2022, this advice is still relevant! If you mess around with compatibility levels, you can absolutely change cardinality estimations in ways you didn’t expect.
Read on for more information, including examples where cardinality estimation has improved with SQL Server 2022 and where it has gotten worse.
Comments closedAmit Kapila notes an improvement in replication capabilities:
In my last blog post, Evolution of Logical Replication, I mentioned the future development of a feature to allow “upgrades of logical replication nodes.” The upcoming release of PostgreSQL 17 includes this feature. Previously, after major version upgrades (via pg_upgrade), users couldn’t immediately connect and write data to logical replication nodes. This was because the slots were lost during upgrades, preventing replication from continuing. As a result, new writes wouldn’t get replicated, causing data on both nodes to become out of sync. As explained in this blog post, users had to block applications from writing until the replication setup was re-enabled after the upgrade.
Read on to see how PostgreSQL 17 changes things.
Comments closedSakshi Gupta provides a public service announcement:
From November 1st, any Azure SQL server left with the “Select an option” or “NONE” setting (where “NONE” means no enforced minimum TLS version) will only allow connections using TLS 1.2 and TLS 1.3. Connections using TLS 1.0 or TLS 1.1 will be rejected. It is critical for all customers to configure their servers correctly and ensure that their client applications can operate with TLS 1.2 or higher.
Pretty much any SQL Server client or driver that Microsoft released from 2016 forwards will support TLS 1.2, so for most organizations, this should be as simple as enabling the option in development and ensuring applications connect as expected.
Comments closedSteve Jones reminds you to check those cumulative updates:
How can I quickly get a CU patch for a system that’s out of date? I’ll discuss that situation.
You might think you get to patch every instance every few months, and you may be able to. But most of us have laggards in any decent-sized estate. Someone always wants to avoid patching, or skip patching on the day you’ve scheduled every other system.
Steve’s solution involves using Redgate Monitor, though you could also do this on your own or using something like dbatools to get information about your estate.
Comments closed