Skip to main content

DataOps General FAQs

This document contains a list of general FAQs divided up into the following categories:


This category includes the following questions:

Why does my compare not show any changes?

This is how DataOps works; it only compares unidirectional or forward changes, not backward changes.

Is the order of input important?

In short, yes, it is. Think of Git Compare as a merge request. If you want to merge the changes in feature branch A to the main/master branch, the valid input order is as follows:

  • Source: A
  • Target: main/master

In this scenario, Git will show the changes as expected. But when you try the input as follows:

  • Source: main/master
  • Target: A

Git will show that there is nothing to compare. This is because Git Compare checks the head of the main/master branch and shows it is behind the target branch.

If you find yourself in this situation, you can always swap the inputs around or force the contents of one branch to another, as demonstrated in the Git in 30 Seconds guide.


This category includes the following questions:

Why do SOLE logs show warnings while creating a new environment?

When you start SOLE, it will first try to import objects in case they do exist in Snowflake. If your objects are new and should be created by SOLE itself, the operation fails and you get a few warning messages which indicate that this is expected behavior because simply there is nothing to import from Snowflake.


This category includes the following questions:

How do I disable the Snowflake Query Cache?

It is not a good idea to disable the Snowflake Query Cache. However, in some scenarios, it is useful to be able to do it, for example, during performance testing.

You can achieve this by adding a pre-hook to the model in question, as the following code snippet shows:

pre_hook="alter session set USE_CACHED_RESULT = FALSE",


The architecture category includes the following sub-categories and questions:


This sub-category includes the following questions:

Can I load data from S3 to a Snowflake tenant on Azure?

Yes. The performance is a little slower, but functionally, this works fine.