CREATE TABLE dbo.POSCustomers AS SELECT is the way to go, since CTAS lets you build a new table with a select query in Fabric warehouses. Then you'll want FROM lakehouse1.dbo.customer so it pulls from the right source using three-part naming. Pretty sure, unless your workspace has some odd permissions setup that blocks cross-engine queries.
CREATE TABLE dbo.POSCustomers AS SELECT, FROM lakehouse1.dbo.customer. CLONE is a tempting distractor, but it just copies structure or data as-is and doesn't let you filter columns or build a new table from a query result. I saw similar logic in practice sets so I think this is correct, unless Fabric changed something very recently.
Anyone know if the Microsoft docs lab for Fabric covers CTAS with cross-engine selects or is it just mentioned in the official guide? Trying to confirm before exam day.
Anyone else remember having nearly this same scenario in Fabric sandbox labs? I think the CTAS pattern is what they want since you can pull only certain columns and use cross-database (lakehouse1.dbo.customer). Not totally sure if any recent changes broke that, but it's matched what I've seen so far.
Yeah, CREATE TABLE dbo.POSCustomers AS SELECT makes sense for this. CTAS lets you pull specific columns and works between lakehouse and warehouse, unlike CLONE which just copies structure/data. Worked for me in practice, unless Fabric updated CTAS behavior.
