Where to monitor jobs in fabric which are running as fabric individual notebooks and not as pipeline?

Hi @Josh Allan-Beer I have use logic apps to move data from share point as source. During this task, I had to dump the data first to ADLS Gen2 and then add this as short cut to the lakehouse. After this I created delta tables with some extra transformation. Hope this helps!

You can back up Fabric Delta Lake tables by copying the table's files and _delta_log to a blob storage . For warehouse you can move the tables to lakehouse and then to storage account. You need to come up with some mechanism that will do this for you. You can use notebooks or pipeline to copy the data. This functionality needs to be created by you or team who is responsible for looking after Fabric as whole (i.e. Admin )

Not that I am aware of!

@Nachiket Kamat Ideally when you design incremental process. The first step is always to have a switch to toggle between full load or incremental. When you plan to go live, most probably it will be full load initially because source team will have the data ready, While we are still working on the design, implementation and testing. Anyways, if you have incremental configured based on lets say on some date (e.g. file process date, last run date, max run date), here you need to either comment out that one line of code which brings only deltas each time or some how hack this date to previous date from which you want to bring the data. This essentially will act as full load and then change back the date to what it was before so that next time when it runs, it will only bring new rows. Alternatively, create a new table with full load and then point the deltas to this table going forward.

@Nachiket Kamat hmmm . I may have miss read it 🤔

@Nachiket Kamat pls. see answers to your questions below= 1. only lakehouse 2. yes 3. yes 4. & 5. To use warehouse data in a Lakehouse, you must first create a Lakehouse and then create a shortcut within the Lakehouse that points to your warehouse tables.