<@UER9Q3SGM> Agreed. It's so "Black box" like. wit...
# general
r
@KevinJ of Kansas Agreed. It's so "Black box" like. with no visibility into and no ability to manage that section, how are we possibly supposed to do anything about it?
a
Just went through this a couple of months ago. Very painful. At the end of the day your historical transaction data is piling up, and Oracle is starting to make people pay. In the end they did include system notes in the total data number, but gave us a 'deep discount' to offset that because it isn't supposed to count. So in the end you can't even really tell what the heck you're paying for.
k
How far over were you and how many transactions do you have in the system?
a
@KevinJ of Kansas total storage at the time was 75GB, they said. we all know that's not really a lot in the scheme of things, my phone holds a lot more than that! i do not know how many transactions we have (started using NS in 2013) - but I filled out an assessment sheet breaking down # of transactions per day, how many items, customers, etc. we did not have enough to warrant tier pricing - so we're small. bottom line is they could not or would not break down EXACTLY what's making up that 75GB. I fought it as much as I could, demanded to speak to our rep's manager and did - but it was only gonna end one way.
as a result, my boss wants to explore offloading old transaction data and storing it elsewhere. ugh. ever heard of anyone doing that?
k
I don't think what you want to do can even be done safely
That would require deleting transactions which would impact GL history
a
I spoke to a consultant (who was working on something else for us at the time) that said it was feasible, but we did not get in to detail. i agree - horrible idea. but now one of my goals for the year is to figure out how to do it! I think it's best i just prove its a bad idea.
k
Let's start with order of operations... You would need to delete customer payments, then invoices then sales orders then estimates. Same concept would apply on purchasing side.... Bad stuff happens to deleting linked transactions
You would be better off exporting your data then doing a new subsidiary then importing what you want to keep then validating then deleting your old transactions and subs
Well, not deleting the sub, but inactivation of it.
Also, you straight up can't delete certain transactions like refunded or voided no matter how you try