Why are extractions sometimes referred to as KA? And why are there tables that like T_KA_Header? I am looking for this definition for training purposes. Those of us who are newer in the organization refer to extractions as extractions, but we often get request from more tenured coworkers that say do this or that with KA #XXXX. It would be helpful to know why it used to be called KA , what the K and the A stand for, and when it changed.
Thanks,
Ashley
I believe it comes from something like "Keycode Assignment". Does that help? I think that probably doesn't help.
Sounds good to me!
I believe Gawain is correct. That said, extractions have been called extractions for at least 14 years. Are the people who call them KA mostly working in SQL? As you noted, for the most part that naming convention is visible in the tables. I'd find it quite surprising if someone who primarily uses extractions in the application were not calling them extractions.
Oh, and speaking of "KA", from time to time I'd recommend looking through your SQL Server Agent jobs for KA_XXXXX jobs with old start dates. Extractions that fail (or have some other issue) are often not cleaned up properly. I check them every month or so and then put in a request with RAMP to remove them.
No, actually our Vice President of Marketing sends emails with phrases like "is segment 100 in KA 7719 up to date?" and he does not use SQL. He may have adopted this lingo from our previous DBA. Thanks for the clarification! It will help me answer the questions other coworkers ask me now that I am the DBA.
Thank you! I just looked and there were 15 of them!! Since we are self hosted - should I just delete them??