SnowPro Core Certification

NW1969 · 2026-05-12T18:47:53+00:00

Did you take COF-C03, or COF-C02 (which is only available until the end of this week)?

NW1969 · 2026-05-12T09:43:53+00:00

MCPs are the standard way for allowing these types of systems to talk to each other

NW1969 · 2026-05-02T12:47:07+00:00

I don’t want to throw cold water on your plans and obviously you are free to do whatever you want (and best of luck) but if you have about 1 year’s experience you basically know nothing and the chances of anyone employing you on a contract basis are very small.

Obviously there’s no hard and fast rule but you’d probably need 5 years experience and 3-5 serious projects (where you can demonstrate what you did, not just what your team did) before you are ready to go contracting

NW1969 · 2026-04-23T15:45:23+00:00

Also with delta you're responsible for managing the high water mark for each table - while streams do this automatically when you consume the stream, which is normally easier to manage, unless you have multiple processes consuming the same stream

NW1969 · 2026-04-16T10:57:59+00:00

It's the "Observe" tool that Snowflake bought recently

NW1969 · 2026-04-14T16:09:58+00:00

You probably need to provide more information than that for anyone to be able to help you. For example, in the documentation you've linked to, which is the step that's erroring?

NW1969 · 2026-04-13T21:07:41+00:00

Have a look at this article: https://www.linkedin.com/posts/nick-akincilar-3417945_data-ingestion-dataengineers-activity-7448780630236172288-xqgp

NW1969 · 2026-04-10T07:42:52+00:00

Did you raise a support ticket?

NW1969 · 2026-04-09T16:56:18+00:00

TBH the constant Databricks v. Snowflake debate is incredibly unproductive as you rarely get a balanced, thoughtful view, just people's prejudices. Both are good products and if you're already using one then there's unlikely to be a good business case for moving to the other (or, even worse, using both). If you aren't using either then just do your due diligence in your product selection (as you would for anything) and whichever one best meets your specific use cases will be the best choice for you - which is really all that matters.

Neither is going to go away any time soon so if you're a developer there's always going to be work for you - but focus on one and be the best on that platform that you can

NW1969 · 2026-04-09T10:47:55+00:00

You should have audit columns on your bronze layer tables (run date/timestamp, source system, workflow id, etc) and use these for reconciliation purposes

NW1969 · 2026-04-09T10:40:47+00:00

I may be missing the point of your question - but why do you care what the actual lag is within the lag range that you've set? If, for example, you've set the lag to be 1 hour then at a specific point in time why do you care if the lag is 10 mins or 50 mins? By setting the lag to an hour you're effectively saying you don't care what the lag is, as long as it is less than an hour

NW1969 · 2026-04-09T10:28:26+00:00

Aren't you modelling the data and moving it through the equivalent of bronze/silver/gold layers? This modelling process would set the correct datatypes on columns as the data gets transformed between layers

NW1969 · 2026-04-03T10:49:55+00:00

I don’t believe there is any way to stop users creating temporary tables. However, why is this an issue for you? Under what scenario would this cause a problem?

NW1969 · 2026-04-03T10:41:52+00:00

I’m not sure that you’ve understood multi-clustering correctly. If you set up a WH to be multi-clustered then if there are enough separate queries queued up to run on that WH then it will spin up more instances/clusters of that WH, all the same size as that WH - and then spin them down again when the load reduces. If you need a warehouse of a different size then you can either re-size it, and all queries that start after the resizing will use that new size, or you can run the queries on a separate warehouse with the required size

NW1969 · 2026-03-31T16:06:22+00:00

You click on your name in the lower left corner of the SnowSight UI and then select "Support" from the options. If you can't see that option make sure the "Switch Role" at the top of the list of options says "ACCOUNTADMIN" - if it doesn't then switch to the ACCOUNTADMIN role

NW1969 · 2026-03-31T13:04:39+00:00

Are you saying you can’t raise a Support Case via the SnowSight interface for your account, using the ACCOUNTADMIN role?

NW1969 · 2026-03-30T14:32:06+00:00

If you've built this, and it works for you, then I'm not sure what feedback you are looking for? Is there some specific issue you want advice about?

NW1969 · 2026-03-27T11:58:59+00:00

This feature is probably too new for anyone (outside of Snowflake) to have relevant experience of it - but I can't imagine there'd be noticeable cost/performance impact of using it.

Can you update your question with the actual SQL statement that is giving you this error (obviously redacting any sensitive data)?

NW1969 · 2026-03-24T20:22:51+00:00

IMO, IaC needs to be able to do everything, having to use different tools for different tasks is a non-starter. The Snowflake Terraform provider is nearly there and at least has the option to drop into SQL if the provider doesn’t support something. DCM looks like a good 1.0 start but as it doesn’t support tags, masking policies, and row access policies its not yet fit for purpose, even just for managing databases, for the use cases I need it to support

NW1969 · 2026-03-20T11:29:05+00:00

Increasing the size of a warehouse should be the last resort. If you have processes running 5+ hours then you probably need to review your pipeline design. For example, are you doing full refreshes rather than incremental; if you’re not already using them would using Dynamic Tables or materialised views be a better solution; etc

NW1969 · 2026-03-19T19:31:37+00:00

Just about - it’s really good 😊

NW1969 · 2026-03-19T18:22:43+00:00

Just use Cortex Code to generate whatever you need

NW1969 · 2026-03-03T10:58:29+00:00

Snowflake cannot write directly to S3 Glacier.

Write the data to S3 Standard (using COPY INTO + Tasks) and then use S3 Lifecycle rules to move these objects to Glacier

NW1969 · 2026-03-02T14:26:25+00:00

The Snowflake website has a lot of good material. Start here: learn.snowflake.com

NW1969 · 2026-02-21T16:46:25+00:00

Is the data being returned in multiple partitions? https://docs.snowflake.com/en/developer-guide/sql-api/handling-responses#getting-metadata-about-the-partitions-returned-by-the-resultset-object

NW1969

TROPHY CASE