Merge pull request #185259 from jovanpop-msft/patch-233

uery failed because of a topology change or compute container failure

Author: PRMerger19

articles/synapse-analytics/sql/resources-self-help-sql-on-demand.md

@@ -541,6 +541,12 @@ You should reload your legacy data with the higher version of Spark, and use the
 spark.conf.set("spark.sql.legacy.parquet.int96RebaseModeInWrite", "CORRECTED")
 ```
 
+### Query failed because of a topology change or compute container failure
+
+This error might indicate that some internal process issue happened in the serverless SQL pool. File a support ticket with all necessary details that could help Azure support team to investigate the issue.
+
+Please specify in the support requests anything that might be unusual compared to the regular workload, such as large number of concurrent requests or some special workload or query that started executing before this error happened.
+
 ## Configuration
 
 Serverless pools enable you to use T-SQL to configure database objects. There are some constraints, such as - you cannot create objects in master and lake house/spark databases, you need to have master key to create credentials, you need to have permission to reference data that is used in the objects.