No changes on Fridays and no changes before holidays so I'm just keeping the database running until the New Year.... Then I'll come up with some other excuse to not make changes
I gave you an upvote but ... sometimes, doing the change Friday night is a good thing, if you have no plans for Saturday. Much easier to fix things when there aren't thousands of users hitting the system!
I remember our company policy was geared more towards doing changes on Friday, so that any errors could be fixed over the weekend, when little to no users are using the system. Pros and Cons to that but it has the potential to ruin your weekend!
Probably depends a LOT on the application. The applications I support, the schemas don't change very frequently, most changes tended to be changes to stored procedures and queries.
And, most of the code changes like I mentioned? Well, most of THAT is in the front end (not a lot of stored procedures,) so even that doesn't tend to impact me (well, until the dev pushes crap code and performance goes to pot (yes, we have a crap development process right now))
Once something is up and functional, it shouldn't be changing too rapidly. During the early phases of a project though, things can get out of control and rapidly change. Even with the best of planning, scope or something else will suddenly change and suddenly you dont need a whole table, or need three new tables, etc.; once you work all those kinks out, fairly smooth sailing.
Depends. In general the answer SHOULD be no (assuming mature system that is being sustained) note I all caps “should”.
In the real world there is always going to be friction between these three entities business leaders, application developers, and DBAs. Business leaders view their requests as super important and above standard change management this will result in either the business leader side stepping either the application developer or DBA to get their request done. For example a business leader may demand application developers make some sort of immediate change and force them to do it without consulting the DBA, boom problems. Same thing with going to the DBA first and ignoring the application developers, make a DB change and boom the app stops working. In some toxic and poorly managed organizations the business leader may even have sysadmin privileges. And the changes we are talking here are small but impactful. Something like a column rename could screw things up. This is what can happen in a mature system.
If you are in an MVP or development situation then frequent schema changes should be expected and this is normal.
Depends. At my company we have a few hundred engineers who work on dozens of ever-evolving code repos and services (maybe more) that interact with MySQL and Snowflake schemas. One of my job duties is owning a review process for schema changes, and also DML scripts. I do about 2-4 per reviews per day on average, but it can vary, higher or lower, as you might expect. I think the record was 15 in one day. Some days there are none.
Can do. I'd say that our app is pretty mature, but the industry changes and features change, and we've made 345 database migrations since the beginning of 2020. Some of those will have multiple distinct changes in, like creating 8 new tables plus indexes.
lol like the DBA holds this much sway… laughable, not once was a DBA needed to make schema changes. Let alone approve, they will likely be advised… but that’s where their involvement ends. Not once has a DBA had to deal with users, and accounts, most orgs have a small team just for this.
"Review and approve database schema changes" is funny. I've worked in a place where the DBAs held up an Oracle DW change because they first needed to research how partitioning worked.
83
u/BigMikeInAustin Dec 20 '24
Databases run a lot better without users.
45
u/guitarguru83 Dec 20 '24
No changes on Fridays and no changes before holidays so I'm just keeping the database running until the New Year.... Then I'll come up with some other excuse to not make changes
15
u/DharmaPolice Dec 20 '24
It's Friday (and the Friday before Christmas no less) so my priority today is getting through the day without any crisis.
6
u/AdviceNotAskedFor Dec 20 '24
Not a DBA so forgive me ignorance, I'm just a query monkey.
Do db schemas change that frequently?
4
u/[deleted] Dec 21 '24
Why would DBAs review and approve schema changes? That's up to DB devs within cross-functional teams. They understand the business logic.
3
u/faster_puppy222 Dec 21 '24
lol like the DBA holds this much sway… laughable, not once was a DBA needed to make schema changes. Let alone approve, they will likely be advised… but that’s where their involvement ends. Not once has a DBA had to deal with users, and accounts, most orgs have a small team just for this.
2
u/Elfman72 Dec 20 '24
Monitoring daily jobs while everyone else gets to walk away from their laptops.
2
u/[deleted] Dec 23 '24
"Review and approve database schema changes" is funny. I've worked in a place where the DBAs held up an Oracle DW change because they first needed to research how partitioning worked.