The agent log is the whole thing that the command ran, so its ALL the history of the run, not just the failure.

When you run index optimise manually you see...

dupe post

As you have "LogToTable" enabled, query the command log table and return anything which doesn't have an error code of 0, this will give you what failed and the error...

Sam, you didn't answer Jo's point above.

Are you actually using IndexOptimise correctly?

Have you read Ola's documentation to verify your job is actually only doing statistics maintenance and not also index...

I am assuming this is a SQL Server Login you are having troubles with?

This issue is known as the orphaned user issue, plenty to read up on the net about...

Set the database to offline, then no one can access it at all, then if you need to failback you just set it back to online

ALTER DATABASE <dbname> SET OFFLINE...

It may be quicker to create a new database with the correct structure and size, and then copy data from the large DB to the correctly sized DB, and rename...

Correct, original question is a bit open to interpretation as to what is going on.

500GB in table but DB is 2.6TB, is that a 600GB MDF and a 2TB LDF,...

Also what is the "log_reuse_wait_desc" from sys.databases for the database in question?

Azure SQL Database is a PaaS offering, as such you hand off management to Microsoft.

Certain functionality for Azure SQL DB must be done in the portal, others must be done...

If you used the AdventureWorksLT database as the sample you should see the "SalesLT" schema and objects in the DB, otherwise it wasn't selected at creation time.

And what have you searched on said topic?

A simple search on this topic will yield a plethora of results.

If you have issues with a specific method then by all means...

https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/join-a-secondary-database-to-an-availability-group-sql-server?view=sql-server-ver16

https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/start-data-movement-on-an-always-on-secondary-database-sql-server?view=sql-server-ver16

It's a bit more involved.

On the secondaries you need to do the restores manually, so you need to get the full/logs all restored and the final one done with NORECOVERY

Then...

The Managed Instance link feature uses distributed availability groups to extend your SQL Server on-premises Always On availability group hosted anywhere to Azure SQL Managed Instance in a safe and...