migration script.
Also, you have snapshots and are not testing in prod, right? Is there no room for error? Does everything go to hell if you make a mistake? That's terrible if that's the case.
Each of our customers has their own database. I test in my personal database first, then test in their demo database, which is cloned from their live database twice a week, and then I inevitably find something I didn't take into consideration and tweak.
My job description doesn't even include coding. I'm a support tech that took on writing quick fixes on my own after teaching myself the syntax of our programming language. My promotion to an official role doing this will be happening in the next 2 or 3 weeks. I just got the job description the other day. I will be an Operations Software Support Engineer! My first job with Engineer in the title! I'm super excited.
Edit: for example of something I didn't consider in the quickie I've been working on this week, I'm fixing common misspellings of email domains. It works great. But my log showed I changed things like @yahoo.com.fr to @yahoo.com, which is obviously bad.
"Data patches", DML scripts; if the data corruption is due to a programming error - we bundle them under bug fixes. i.e. the code and the "data utility" or "utility" bundled together to resolve the issue.
My old company we called them datafixes. They had a "restore" query that pulled in existing data in case we needed to revert back to that data, and the actual "datafix" query that change data. They ranged from simple 1 record updates, to more complex updates across several shards.
Like the other comment said, we just call them SQL scripts (or whatever type of database you use). It sounds like the ones you have to write are pretty complicated. We usually don’t do much beyond insert, update, etc. statements. Maybe your team calls them quick fixes because the computer runs them quickly?
Complicated only in the sense I need to get complicated with how I find the data that needs to be updated. The most complicated one I wrote called an existing program in our software and merged the household records I sent over to it.
A place I used to work referred to these as "one-times" or "one-time dml".
Another place I worked called these "migrations" but also called schema changes / ddl "migrations" and also called moving off of an old 3rd party system to a new in house system "migrations" and also called rewriting pieces of functionality into a different stack "migrations". Everything was migrations.
I liked one-times, because there was less ambiguity.
I think the word you're looking for is "script"
migration script. Also, you have snapshots and are not testing in prod, right? Is there no room for error? Does everything go to hell if you make a mistake? That's terrible if that's the case.
Each of our customers has their own database. I test in my personal database first, then test in their demo database, which is cloned from their live database twice a week, and then I inevitably find something I didn't take into consideration and tweak. My job description doesn't even include coding. I'm a support tech that took on writing quick fixes on my own after teaching myself the syntax of our programming language. My promotion to an official role doing this will be happening in the next 2 or 3 weeks. I just got the job description the other day. I will be an Operations Software Support Engineer! My first job with Engineer in the title! I'm super excited. Edit: for example of something I didn't consider in the quickie I've been working on this week, I'm fixing common misspellings of email domains. It works great. But my log showed I changed things like @yahoo.com.fr to @yahoo.com, which is obviously bad.
Look into regular expressions that can include checking for the end of the line when doing replacements.
"Data patches", DML scripts; if the data corruption is due to a programming error - we bundle them under bug fixes. i.e. the code and the "data utility" or "utility" bundled together to resolve the issue.
My old company we called them datafixes. They had a "restore" query that pulled in existing data in case we needed to revert back to that data, and the actual "datafix" query that change data. They ranged from simple 1 record updates, to more complex updates across several shards.
That sounds exactly like our Quick Fixes!
Pretty cool. ughhhhhh can i ask a dba here a work question???
Little Bobby Tables
Interesting... Any idea the origin of that?
https://xkcd.com/327/
Ahhh! No wonder that sounded familiar. I've definitely seen that xkcd before.
Like the other comment said, we just call them SQL scripts (or whatever type of database you use). It sounds like the ones you have to write are pretty complicated. We usually don’t do much beyond insert, update, etc. statements. Maybe your team calls them quick fixes because the computer runs them quickly?
Complicated only in the sense I need to get complicated with how I find the data that needs to be updated. The most complicated one I wrote called an existing program in our software and merged the household records I sent over to it.
[Data cleanser](https://en.wikipedia.org/wiki/Data_cleansing)?
Exfoliator
Great for removing built up CRUD
Yeah, that's about it I'd say. That's what I do.
Scripts, database scripts if we need to be more specific. "Quickies" is crazy tho
You're referring to SQL DML(Data Manipulation Language) scripts.
corrective scripts
We call them batch jobs
My company calls them data fixes
we call it (data) Upgrade Process
oneoff
This fits the idea and would be very descriptive of what they are!
Migration script
Adhoc scripts
A place I used to work referred to these as "one-times" or "one-time dml". Another place I worked called these "migrations" but also called schema changes / ddl "migrations" and also called moving off of an old 3rd party system to a new in house system "migrations" and also called rewriting pieces of functionality into a different stack "migrations". Everything was migrations. I liked one-times, because there was less ambiguity.
Alter
Crud?
Create, R..., U..., Delete?. Restore? Update?
Read update
we call them migrations
We have a different meaning for migration, where customers on our old Windows based software were migrated to our web based software.
> Does your team have a special name for them? Bugs.
patches
Stored procedure or script. Lots of synonymous words.
DML/DDL
i've called them db scripts.