The TRUNCATE TABLE statement is a DDL (Data Definition Language) operation that removes all rows from a table but leaves the table metadata intact, including the table schema, description, and labels. Since TRUNCATE is a metadata operation it does not incur a charge.

@adesojialu1051

Жыл бұрын

How did you write the ddl, which language,is it in SQL?

@LearnGoogleCloudwithMahesh

Жыл бұрын

@@adesojialu1051 Sorry, I did not understand the question

Learning from mistakes and sharing with everyone is important to save the cost, It is very informative!

Great video Mahesh! Thanks.

Great.. Do extend this for remaining services as well!!

@LearnGoogleCloudwithMahesh

2 жыл бұрын

Sure, Shanmuk

very nice tips

thanks sir

@LearnGoogleCloudwithMahesh

Жыл бұрын

Thanks Gaurav

Hi Mahesh, Excellent Work you are doing, I have one small query, can we implement some rules to preempt the BQ queries that would run an excessive workload (e.g. query processing more than 50Gig, or similar spikes)? Please share your comments on this.

Nice tips ,how to analyse reports here in bq for performance part.

Great Tips Mahesh, I think we can also do partitioning if we know the user is firing a query on particular column like region frequently and as I know if single partitioning goes beyond 1 Gb then we can go for clustering so less data can be scanned and it can save cost

@LearnGoogleCloudwithMahesh

Жыл бұрын

True

Hi Mahesh, I think we can consider to use the partitioning feature? to have cost optimization.

@LearnGoogleCloudwithMahesh

2 жыл бұрын

True

Hi Mahesh....Do you provide GCP and Devops training too

But truncate can be done by running the query in BQ which incurs certain charges right?

@LearnGoogleCloudwithMahesh

2 жыл бұрын

No it will not incur cost

is it the network cost that is optimized if we create in the same region?

@LearnGoogleCloudwithMahesh

Жыл бұрын

Network cost - Egress will be reduced