One of the biggest issue that you might experience in Managed Instance is reaching storage limit or finding out that you don't have enough CPU. In this case you would need to get the bigger instance; however, this is not instant operation. In this post, you will see how you can monitor resource usage and send email alerts if there is a risk that you might reach the limits.
2023-12-20
Azure SQL Managed Instance is fully managed SQL Server instance hosted in Azure cloud. Managed Instance introduces some limits such as max log write throughput that can slow down your workload. In this post you will see how to identify write log throughput issue on Managed Instance.
2023-12-11
2023-07-05
300 reads
2023-06-21
339 reads
2023-06-14
369 reads
2023-06-07
338 reads
2023-05-31
369 reads
2023-05-24
432 reads
2023-05-17
373 reads
2023-05-10
347 reads
If you spend your days tuning queries, managing pipelines, or keeping a production database...
I’ve been rebuilding my three-site SQL Server demo lab, and I ran into something...
By SQLPals
SQL Server gMSA: Why DBAs Still Aren't Using It in 2026 ...
Comments posted to this topic are about the item Never is Not the Policy
Comments posted to this topic are about the item Automating SSAS Multidimensional Security Audits...
Comments posted to this topic are about the item Rebuilding All Indexes
I have added a few indexes to one of my tables in SQL Server 2025:
ALTER TABLE dbo.CustomerContact
ADD CONSTRAINT PK_CustomerContact
PRIMARY KEY (CustomerID);
-- Create index on CustomerEmail
CREATE INDEX IX_CustomerContact_CustomerEmail
ON dbo.CustomerContact (CustomerEmail);
CREATE INDEX IX_CustomerContact_CustomerEmail
ON dbo.CustomerContact (phone);
I then do this to disable one index:
alter index IX_CustomerContact_CustomerPhone on dbo.CustomerContact disableI see this when I check the index status:
I decide to rebuild all indexes with this command:
ALTER INDEX ALL ON dbo.CustomerContactAfter I do this, what will I see for the index status? See possible answers