Forum Discussion
publicly available data
I am taking a class on Fabric and we are copying publicly available data into our warehouse using the SQL endpoint.
We are using these two tables.
Yes, I tried that solution and it was still the low counts. I finally found the new URLs for the data. It actually was moved. thanks
COPY INTO [dbo].[dimension_city] FROM 'https://fabrictutorialdata.blob.core.windows.net/sampledata/WideWorldImportersDW/parquet/full/dimension_city' WITH (FILE_TYPE = 'PARQUET');
COPY INTO [dbo].[fact_sale] FROM 'https://fabrictutorialdata.blob.core.windows.net/sampledata/WideWorldImportersDW/parquet/full/fact_sale' WITH (FILE_TYPE = 'PARQUET');
4 Replies
Hi trindadsth,
Have you had a chance to review the solution shared by ShivekMaharaj? If the issue persists, feel free to reply so we can help further.
Thank you.
Yes, I tried that solution and it was still the low counts. I finally found the new URLs for the data. It actually was moved. thanks
COPY INTO [dbo].[dimension_city] FROM 'https://fabrictutorialdata.blob.core.windows.net/sampledata/WideWorldImportersDW/parquet/full/dimension_city' WITH (FILE_TYPE = 'PARQUET');
COPY INTO [dbo].[fact_sale] FROM 'https://fabrictutorialdata.blob.core.windows.net/sampledata/WideWorldImportersDW/parquet/full/fact_sale' WITH (FILE_TYPE = 'PARQUET');
HI trindadsth,
Thanks for confirming. Glad you found the updated URLs and resolved the issue after the data was moved. The new COPY INTO paths should load the expected data correctly. So Accept your reply as the solution, as it will be helpful for other community members facing the same issue.
Thank you.
Hi trindadsth,
I suspect the load may actually be fine and you’re just seeing a limited preview of the table.
If you’re checking the data from the Warehouse explorer or a generated TOP query, that does not show the full row count. For example, Fabric has a Select TOP 100 rows option in the Explorer, and the Data preview is also intended only as a sample of the table.
I’d run a count directly against the two tables instead:
SELECT COUNT(*) AS CityRows FROM dbo.dimension_city; SELECT COUNT(*) AS SaleRows FROM dbo.fact_sale;If those counts return the expected larger numbers, then nothing is wrong with the COPY INTO operation. You were just looking at a preview/query that limits the number of rows displayed.
If the counts themselves really are only 10 and 100, then I’d check the exact COPY INTO statements and the Messages output from the load, because COPY INTO from those Parquet files should not normally stop after an arbitrary number of rows.
I’d start with the COUNT(*) though, since that will tell you straight away whether this is a loading problem or just what the Fabric UI is displaying.
