Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Did you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now

Reply
Fabricator101
Frequent Visitor

WebRequestTimeout When Importing Schema From ODBC Source

Hi

 

We are trying to migrate our tables from Sybase database. While creating copy activity for some of the tables, during import schema in table mappings, we get the following error:

 

Error code
WebRequestTimeout
 
Details
Failed to import source schema. A task was canceled. Activity ID: 
 
Any idea why this timeout is happening or how to increase the amount of time for the import schema option to complete? It will be very time consuming for us to manually create each column mapping with 70+ columns for many tables. Please advise.
 
Thanks
1 ACCEPTED SOLUTION
Fabricator101
Frequent Visitor

Hi

The import schema source table has large amount of rows. Due to this fact, import scema fails to gather/sample data types of columns. This in-turn gives web timeout. The solution, that I have found is to use query instead of table name in the source parameter. And do a SELECT TOP 100 * from [table_name]. This will allow the mapping within web time limit. Once mappings are done, change source query to source table name.

View solution in original post

2 REPLIES 2
Fabricator101
Frequent Visitor

Hi

The import schema source table has large amount of rows. Due to this fact, import scema fails to gather/sample data types of columns. This in-turn gives web timeout. The solution, that I have found is to use query instead of table name in the source parameter. And do a SELECT TOP 100 * from [table_name]. This will allow the mapping within web time limit. Once mappings are done, change source query to source table name.

v-hashadapu
Community Support
Community Support

Hi @Fabricator101 , Thank you for reaching out to the Microsoft Community Forum.

 

The timeout issue during schema import from your Sybase database could be due to network latency, large schema size, inefficient queries, or insufficient timeout settings. To address this, increase timeout settings in Microsoft Fabric Pipelines and Linked Service for Sybase, use schema mapping export/import to avoid repeated imports, switch to Dataflow Gen2 for large tables, use Fabric Spark Notebooks for complex migrations, and optimize Sybase performance by rebuilding indexes and updating statistics.

 

If this helped solve the issue, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.

Helpful resources

Announcements
April Fabric Update Carousel

Fabric Monthly Update - April 2026

Check out the April 2026 Fabric update to learn about new features.

Fabric SQL PBI Data Days

Data Days 2026 coming soon!

Sign up to receive a private message when registration opens and key events begin.

New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.