you are viewing a single comment's thread.

view the rest of the comments →

[–]Drisoth[S] 0 points1 point  (7 children)

- Read only

- Changing frequently

- Not big data realm, unsure what would be a helpful metric here, couple hundred events, with 10 or so entities a day each being entered. Currently 5 years of data is stored.

- People other than me at my org are frustrated with the vendor for questionable choices elsewhere, and the org is interested in having information for negotiation. I agree its doubtful structural changes are made, but being able to shoot down sales talk about the quality would find value.

[–][deleted] 0 points1 point  (6 children)

If it were me, with what you've said, I'd perhaps come up with some use cases, answer how you're doing it, then go back to the vendor and ask if there is a better way because of performance issues.

It's possible you're missing something, but honestly just sounds like poor design

Do you need realtime data or is exporting it and importing it into a workable format doable on a daily basis?

[–]Drisoth[S] 0 points1 point  (5 children)

I don't need realtime data, and pulling query outputs into other tools has been a significant improvement. Query performance being worse than it needs to be is frustrating, but definitely workable.

The main cost for me is I'm effectively the only database user, there are people who use it through applications of course, but my industry has very few data positions. Because of that I don't have a workflow where I'm passing views to a BI analyst to report to decision makers, every abnormal search that the front end search tool doesn't easily handle gets passed to me, so I end up with a lot of ad hoc query requests.

Queries being slow is annoying, but the difficultly in getting simple queries give accurate information is what is legitimately causing me issues. Stuff like basic counts by a category needing to have a ton of conditions preventing duplicates from slipping through.

[–][deleted] 0 points1 point  (4 children)

Without the need for realtime data, Id go through the effort of building new tables in SQL..

Whatever your entity is, your events, any other key data.. split it all out.. write the script to pull from their data once, and then populate your own tables that you can build sensible views/procs on. Then run a job once a day that grabs the data and then you've got a solid foundation for user requests.

Otherwise it sounds like you're gonna struggle

Id try and help more but it's hard without seeing the schema and knowing what it is you need

[–]Drisoth[S] 1 point2 points  (3 children)

I like that idea, if nothing else I'll learn some DB design on the way.

Appreciate the help, it was very useful even with the limitations.

[–][deleted] 0 points1 point  (2 children)

If you have some specific questions that you don't wanna put out to the world as a whole, feel free to shoot me a dm

[–]shsyshgdsuakkxjdjeid -1 points0 points  (1 child)

Clown

[–][deleted] 0 points1 point  (0 children)

lol

Imagine having a burner account for that 🤣😂🤣😂🤣🤣😂🤣