[BUG] do not compile unnecessary code when previewing query results in VSCE

[graciegoheen]

Describe the bug

Previewing query results using the VSCE is currently slower than running dbtf show for given SQL query.

anders' understanding is that any "action"/"trigger" will first compile your project before doing anything. where actions can be

• saving a file
• previewing a model
• previewing the compiled sql

note from connie:

We are going to have compile timing telemetry soon, so we can see how much this is impacting UX. My guess is...substantially, since we get anecdotal feedback that the full project compile takes a long time.

To Reproduce

struggling to create a repo since i can't tell which actual commands are run (created #423 to help debug)

Expected behavior

make sure we're not compiling stuff that doesn't need to be compiled in the course of previewing a query

[drewbanin]

@graciegoheen to add a repro to this ticket, @TIHan will check it out

[graciegoheen]

from discussion, sounds like there's an additional issue here where preview query is different in VSCE vs. studio:

• dbtf show -s my_model is just selecting the existing materialized model in the warehouse in Studio (bug - see zoom clip). note: that is different from what's documented

• vs. preview query is actually running the model's SQL in the warehouse

[graciegoheen]

@TIHan do you know what commands are executed when we preview query results in VSCE today? do we compile the entire project?

[graciegoheen]

struggling to create a repo since i can't tell which actual commands are run (created #423 to help)

[graciegoheen]

Our internal data team is running into this too:

preview also seems to first fully compile your project, which makes it VERY slow compared to even Core