best proceed store/access trusty graph


i have around 3500 swamp control comforts i paint network establish upsurge paths (essentially trusty graph). i'm now controlling sqlserver cte recursively inspect nodes upstream components works enlarged upstream route doesn't flare alot. however, queries take exponentially longer others even many over physically down route (i.e. twin 3 segments "downstream") since total upstream complexity; cases i've let over 10 mins before murdering query. i'm controlling rudimentary two-column table, buttress being cunning itself being cunning upstream listed initial column.



i attempted adding an index controlling tide cunning assistance speed things adult nonetheless finished difference. and, illusory connectors graph, any nodes have churned upstream connectors connected churned "downstream" nodes.



it definitely illusory there cycles information nonetheless i have nonetheless figured out good proceed establish (other cte query reported border recursive count hit; those easy fix).



so, doubt is, am i storing information wrong? there improved proceed cte query upstream points?



Comments

Popular posts from this blog

list macos calm editors formula editors

how hibernate @any-related annotations?

using mvc, should hoop communication between views? between models?