Azure Data Factory copy activity scenarios with 'Data preview scenarios' scenarios on specific data types
I've been working on this all day and I've been researching this but I've been banging my head against this for hours... I'm following best practices but I'm working on a project and hit a roadblock. I'm relatively new to this, so bear with me. I'm working with an scenario with Azure Data Factory where a copy activity fails with the behavior message 'Data preview failed' when trying to copy data from an SQL Server database to a Blob Storage. The source table contains a few columns with data types like `DATETIME` and `VARBINARY`, which I suspect might be causing the question. I've checked the data types and they seem compatible with Blob Storage, but I'm still getting this behavior when I try to preview the data in the copy activity. Here’s the configuration for my copy activity: ```json { "name": "CopyFromSqlToBlob", "type": "Copy", "inputs": [ { "referenceName": "SourceSqlTable", "type": "DatasetReference" } ], "outputs": [ { "referenceName": "BlobDestination", "type": "DatasetReference" } ], "source": { "type": "SqlSource" }, "sink": { "type": "BlobSink" } } ``` I've tried adjusting the data preview settings and checked for any transformation settings, but nothing seems to resolve the scenario. I also attempted to run the activity with a smaller dataset, and it worked without errors, which makes me think there might be specific rows causing the failure. Is there a way to debug this further or handle the problematic data types better? Any insights would be appreciated! I'm using Azure Data Factory V2 and have already validated the connection to both the SQL Server and Blob Storage. Additionally, I’ve ensured that the Data Factory has the necessary permissions to access these resources. This is part of a larger API I'm building. How would you solve this? This is my first time working with Json LTS. Any ideas what could be causing this? I appreciate any insights! I'm using Json 3.9 in this project. This issue appeared after updating to Json latest. Am I approaching this the right way?