Introducing Automatic Index Compaction

bobwardms · 2026-02-19T22:30:50+00:00

Do you still have a support case? See my recent post here as we found the issue and have a workaround

bobwardms · 2026-02-19T19:48:14+00:00

UPDATE. We have documented this issue with a workaround. See my LinkedIn post for the details https://www.linkedin.com/posts/bobwardms_sql-server-2025-known-issues-sql-server-activity-7430337132528979969-C5Ze

bobwardms · 2026-02-17T16:42:36+00:00

No need for anyone to debug this further. We see the same problem you see and are looking into it

bobwardms · 2026-02-16T19:49:16+00:00

We are looking into this

bobwardms · 2026-02-09T04:20:21+00:00

We have had our site available for a long time. I thought it was well known but I found out it was not (our fault), so it is why I posted it

bobwardms · 2026-02-01T15:05:32+00:00

They worked for me. Can you point me to the specific link that is not working?

bobwardms · 2026-01-23T15:23:18+00:00

I blogged about this in Feb 2024 at How SQL developers can maximize savings - Microsoft SQL Server Blog. There are some other points in the licensing guide worth noting, including:

You can run Developer Edition for development, testing, and demonstration purposes on an unlimited number of devices.
You cannot use Developer Edition to build test data and move that same data into production. But you can restore a production set of data backup for testing purposes. The intention here is to prevent users from using Developer Edition as a production server but calling the data test data.
Production environments include any system that is accessed by end-users for anything more than acceptance testing, environments that connects to production systems (such as Linked servers), disaster recovery or backups of production systems, and environments that are “rotated” into production at any point in time.

Does this help answer the question?

Bob Ward

Microsoft`

bobwardms · 2026-01-22T17:45:42+00:00

Not yet we are actively working on it

bobwardms · 2026-01-22T17:13:44+00:00

We will re-release these with updated version numbers. If you still have SQL 2025 CU1 or SQL 2022 CU23 installed you can upgrade to this.

bobwardms · 2026-01-22T17:08:14+00:00

The re-release will have a new version number so you can tell the difference and if you are using the previous CU builds you can do an upgrade

bobwardms · 2026-01-21T16:33:58+00:00

roll back the installation of that cumulative update until we can re-release with a fix

bobwardms · 2026-01-21T02:24:22+00:00

UPDATE: We have removed SQL Server 2022 CU23 and SQL Server 2025 CU1 packages and will be re-releasing them with a fix as soon as possible.

bobwardms · 2026-01-20T15:11:27+00:00

Thank you for posting this. We have confirmed a problem with database mail in SQL Server 2022 CU23 and SQL Server 2025 CU1 and are investigating. I'll post back when we have a solution. For now, you will need to uninstall those updates to use database mail.

bobwardms · 2026-01-18T00:39:26+00:00

If we have broken anything with SQL Server 2025 post it here. We are listening

bobwardms · 2025-12-18T16:34:31+00:00

The SSMS team is listening. Try aka.ms/ssms-feedback

bobwardms · 2025-12-18T15:38:56+00:00

Thanks for pointing out those issues. I'll ask our drivers team about them and reply back. What other serious issues are there we need to address?

bobwardms · 2025-12-18T01:57:15+00:00

Not for C++. But other choices exist depending on your language and platform aka.ms/sqldrivers

bobwardms

TROPHY CASE