Rick Heicksen

Rick Heicksen is the Vice President of Sales at Chetu, Inc., a renowned global software development company. He manages accounts in multiple sectors, including Food & Beverage, Agriculture, Transportation, Energy, and IT Service Management. With his expertise in business development and exceptional customer service, Rick has helped many clients grow their businesses. Rick is known for his versatility and ability to keep pace with technological advancements, which has significantly influenced his success at Chetu. He earned his degree from Chapparal Community College and is passionate about staying up-to-date with the latest industry trends. Since joining Chetu in 2019, he has risen quickly and established himself as a thought leader within the Food and Beverage community, helping the company grow into an award-winning organization.

It seems we can’t find what you’re looking for. Perhaps searching can help.

Blogs

T-SQL Tuesday #199 Invitation: Back to on-prem?

By

It’s time for T-SQL Tuesday again! And we’re almost to number 200! T-SQL Tuesday...

Data Skew in Data Engineering: What It Is and How to Fix It

By

You kick off a distributed job expecting it to finish in minutes — but...

Error Deploying GraphQL in Fabric: dm_exec_describe_first_result_set

By

A while ago we suddenly had an error while trying to deploy one Fabric...

Read the latest Blogs

Forums

Secure Cached Plans

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Secure Cached Plans

Complex Data Processing with dbt Python Models: The Fabric Modern Data Platform

By John Miner

Comments posted to this topic are about the item Complex Data Processing with dbt...

Over or Under Provisioned

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Over or Under Provisioned

Visit the forum

Question of the Day

Secure Cached Plans

The DMV, sys.dm_exec_cached_plans, contains rows for each cached plan on an instance. In Azure SQL Database, not every used has rights to every database, as there does exist an instance behind each database. How is security handled for this DMV in Azure?

See possible answers