Next week I’m heading to the Lowry Conference Center in Denver for the RMOUG Training Days. The Rocky Mountain Oracle User Group has put this on for years, and I’ve been honored to speak a few times.
This time I have two sessions, one live and one virtual. The live one will be Flyway tips and tricks, sponsored by Redgate. The virtual one is my Branding Yourself for a Dream Job talk.
Register today and join me to learn about some Oracle and MySQL
Today’s coping tip is to go to bed in good time and allow yourself to recharge.
I need this reminder. Lately I’ve struggled to sleep well, through the night, and I’ve had some rough mornings. It seems this usually happens when I have early meetings, which makes things even worse.
I’m making it a point to get to bed by 10 for a few days and see if that helps me at all.
I started to add a daily coping tip to the SQL Server Central newsletter and to the Community Circle, which is helping me deal with the issues in the world. I’m adding my responses for each day here. All my coping tips are under this tag.
In order to generate migrations, we need to configure Flyway to use a shadow database. This post looks at that process.
This is part of a series of working through Flyway and Flyway desktop to demo database changes. Disclosure: I work for Redgate Software.
This is an empty database where we run the migration scripts to verify them. Since a user might edit or create their scripts, we want to ensure there are no problems with the syntax or execution with other scripts. This is also a place where we keep the “previous state” of your development database and use this to detect the changes you’ve made.
This database gets cleaned, meaning objects get dropped, regularly, so you configure a space for this. It can be a separate database, or just a schema (more Oracle focused).
For me. I’m going to create a new database in postgreSQL to support this. As you can see below, I use the simple CREATE DATABASE syntax.
Once I do this, I go back to FWD and click the “Generate Migrations” tab. The first time I do this (and only the first time), it asks me to configure a Shadow database.
I click this and get a connection dialog, similar to what I have for my development database. In here I enter the credentials for my shadow database, which are similar to my development ones. I test the connection and verify I can connect.
That’s it. Now I’m configured for a Shadow.
The process is similar for other platforms, just with different credentials. If you need to learn more, you can read about this in the documentation.
Today’s coping tip is to get back in contact with an old friend.
This is something I don’t do too often, but I have done a few times. I’ve met a lot of great people in my life. Some I worked with, some I encountered in other parts of life. When I go to the UK, I usually see if I can reach out and get the chance to meet someone I know from there for a meal or drink. Which reminds me, I need to reach out to someone and try to make plans for June.
Around here, I’ve met some really interesting people as a part of coaching. I took time recently to go watch a few kids play that I coached in the past, but haven’t seen in some time. I also sat down with a parent who became a friend, but someone I haven’t seen in a few years.
Always good to see friends, and worth making the time.
I started to add a daily coping tip to the SQL Server Central newsletter and to the Community Circle, which is helping me deal with the issues in the world. I’m adding my responses for each day here. All my coping tips are under this tag.
Voice of the DBA 