启动专用SQL池（dedicated sql pool）后在Synapse Studio中创建表时提示‘Failed to establish connection to server’的问题求助

Let's break down your issue: you can create tables smoothly via SQL Studio, but Synapse Studio keeps throwing a "Failed to establish connection to server" error—even though it worked briefly once before breaking after pausing and resuming your dedicated SQL pool. Your table creation syntax is solid (since it runs without issues in SQL Studio), so the problem is almost certainly tied to Synapse Studio's connection handling, not your query itself.

Here are targeted fixes to try, ordered by how quick they are to test:

• Clear Synapse Studio's cache and restart your session
  First, fully close all Synapse Studio tabs, clear your browser's cache (including cookies and site-specific data for the Synapse domain), then reopen Synapse Studio and reconnect to your dedicated SQL pool. Temporary cached connection data often gets corrupted after pool pause/resume cycles, and a fresh session can wipe that out. You can also test in an incognito/private browser window to rule out interference from browser extensions or persistent cache.

• Verify your dedicated SQL pool's state and resources
  Head to the Azure Portal, navigate to your dedicated SQL pool, and confirm it’s in the Running state (not paused, scaling, or under maintenance). Also check the resource metrics (CPU, memory, storage) to make sure there’s no unexpected resource exhaustion—while SQL Studio connects fine, Synapse Studio’s connection logic can be more sensitive to transient resource spikes.

• Refresh your Synapse Studio authentication
  Log out of Synapse Studio completely, then log back in with your Azure AD account. Expired authentication tokens can cause silent connection failures, even if you appear to be logged in. Double-check that your account has the necessary permissions on the SQL pool (at minimum, db_owner or permissions to create tables)—compare this to the identity you’re using in SQL Studio (if it’s a SQL auth account instead of AD, ensure your AD account has matching access).

• Validate network and firewall configurations
  Even though SQL Studio connects successfully, Synapse Studio might use a slightly different network path. Confirm your client IP is allowed in the SQL pool’s firewall rules. If your Synapse workspace uses private endpoints or VNet integration, check that there are no network security group (NSG) rules blocking traffic between Synapse Studio and the dedicated SQL pool.

• Restart Synapse workspace components (if you have permissions)
  If the above steps don’t work, go to your Synapse workspace in the Azure Portal and try restarting the Synapse Studio service (or the entire workspace if needed). Temporary glitches in the backend service can cause connection issues that persist until a restart.

Just a quick confirmation: your table creation code is perfectly valid, which we already know since it works in SQL Studio:

CREATE TABLE [dbo].[Table] ( col1 int NOT NULL ) WITH ( DISTRIBUTION = HASH (col1), CLUSTERED COLUMNSTORE INDEX ) GO

内容的提问来源于stack exchange，提问作者Ryoss