This is a post containing a query that’ll bring back all schemas, tables, and columns in Redshift or Postgres databases. I’m combining the Redshift and Postgres database blog categories here…
What is this blog about?
Hello and welcome to my tech blog, which is a place for me to store all my notes as I blog away as a software enthusiast.
My area of interest, or niche, very much revolves around Database Administration, so there will be a lot of RDMS related blog posts here, particularly on SQL Server. I spend a lot of time testing random features during my journey as a Database Administrator (DBA). This tech blog is a good place to store notes for personal reference. I do try my best to keep things accurate and informative for those landing on my pages via Google search too though.
If you want to know more about who’s writing this have a look at my about me page here.
I hope you find some of my posts useful and feel free to get in-touch. If anything I say is inaccurate or if you’d like to offer some general feedback please go ahead, I’d really appreciate it.
Certificates & Encryption CSV Files Database Admin Database Backups Data Types Deleting Data Error Messages Exporting Data Featured Git Importing Data Installing SQL Server Linked Servers Linux Admin Logging & Monitoring Measuring Databases Restoring Databases SQL Server Agent SQL Server ETL SQL Server Management Studio SQL Server Processes SQL Server Scripts Windows Admin WordPress Technical Issues WordPress Tutorials WSL
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 does anyone use WHERE 1=1 in their queries? And what does it do? The condition means WHERE TRUE, so it’s just bringing back the same query result as it would without.