Redshift Blog Archives, by Peter Whyte (Database Administrator). Includes Redshift Administration blog posts and SQL Scripts.
Greetings Tech People! If you’ve been following my technical journey on peter-whyte.com, I’m excited to share a new platform that dives into the world of Database Reliability Engineering and beyond –
Some time ago I wrote a blog post on why use WHERE 1=1 in SQL. This time it’s why use WHERE 1=2, but really this can be WHERE 1=9 or anything that isn’t a 1, we just want the false statement.
A handy post to note down the JDBC client driver download. I’m frequently in need of this myself. You can download the JDBC driver from the AWS Docs and then gain your cluster endpoint address from the main Redshift dashboard window Instead of doing the above, you navigate to the Configure tab in the Redshift console and download the JDBC driver &
This post contains a SQL script that will return all schemas, tables and columns in Redshift or Postgres. I’m combining the Redshift and Postgres database blog categories here.
Superusers in RedShift hold the permissions to perform any action in the cluster, the same access as ‘master’ or whatever you named the superuser during creation.
Dropping users in Amazon Redshift is a simple task, but sometimes you may encounter an error message if the user you are trying to drop is an owner of an object in the database, such as a schema, table, or view.
Here’s a simple guide on creating a new AWS RedShift Cluster within a personal AWS test environment. Warning, if you’re testing this AWS Service you have to be rigorous with managing the cluster for billing reasons.
A common SQL question is, why would anyone use WHERE 1=1 in their queries? And what does it do? The WHERE 1=1 condition means WHERE TRUE.
