Forum Discussion
Eventstream custom SQL code not working due to an invalid input name
- 1 year ago
Hi PaxDataEngineer ,
Looks like you havent added the destination. In this case, Lakehouse1 or
wrapping stream names with special characters (like hyphens/underscore) in square brackets is causing the error.
Try using the stream name without hyphen and then validate and check.
Please refer-
From Clicks to Code: SQL Operator under Fabric Eventstream (Preview)
Hope this helps!
Hi PaxDataEngineer
Currently the SQL code editor is in preview and we can expect some challenges with the service.
With that said, I cannot recreate the issue on my development environment.
If I create a custom SQL job to my stream and do not alter it at all, it works OOTB.
Though, I can create the error message if I'm using non-streaming SQL functions and names.
You might already know this, the SQL code behind the Eventstream is the same as the Azure Streaming analytics and is a subset of functionality - you can read the entire docs here: Azure Stream Analytics & Fabric Eventstream Query Language Reference - Stream Analytics Query | Microsoft Learn
I hope you can make it work in your environment
So it does say "no problem detected" when just using the simple "SELECT * INTO [Output] FROM..." but after saving it you can see the error specifying that the stream name is invalid.
- datacoffee1 year agoMost Valuable Professional
Ah yes. I see that.
I guess you are right with the small bug.
My guess it is due to the underscore in your stream name.
Let's see what the Microsoft team here in the community says 😀