Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
We are executing a pipeline that bring data from On Prem.
The steps require to execute the following steps in 1 session
1 ) Run SP which populates a global temp table
2) Access data from the temp table and populate that in Lakehouse.
NOTE : We can not run these two SQL seperately because it will run via seperate session and temp table will not be accesible.
example:
call sp( param1, param2 );
select * from global_temp_table1;
If any of you have implemented this in Fabric pipelines, do share your thoughts.
Solved! Go to Solution.
Hi,
A Table-valued UDF may work better than a Stored Procedure in this case. You can query the results immediately without using a temporary table. You can run just one SQL query then. I'm not sure whether you are able to modify the source to change the stored procedure to a UDF, but here's an example of a UDF (from https://learn.microsoft.com/en-us/answers/questions/1291176/how-to-call-stored-procedure-and-stored-...)
CREATE FUNCTION CustomersByRegion
(
@RegionID int
)
RETURNS TABLE
AS
RETURN
SELECT *
FROM customers
WHERE RegionID = @RegionID
GO
Hi,
A Table-valued UDF may work better than a Stored Procedure in this case. You can query the results immediately without using a temporary table. You can run just one SQL query then. I'm not sure whether you are able to modify the source to change the stored procedure to a UDF, but here's an example of a UDF (from https://learn.microsoft.com/en-us/answers/questions/1291176/how-to-call-stored-procedure-and-stored-...)
CREATE FUNCTION CustomersByRegion
(
@RegionID int
)
RETURNS TABLE
AS
RETURN
SELECT *
FROM customers
WHERE RegionID = @RegionID
GO