DS was honestly the section I struggled with the most before things clicked. The issue usually isn't computational - it's that Data Sufficiency is testing a different skill than Problem Solving. You're not solving for a value, you're deciding whether enough information exists.
One thing that helped me more than anything: I stopped trying to find the answer and started asking "under what conditions would this NOT be sufficient?" That mental shift changed everything. If you can quickly construct two scenarios that give different answers under a statement, you know it's insufficient. If you can't, it probably is.
A few concrete things I'd try:
First, make sure you've internalized what each answer choice actually means. Most people know A/B/C/D/E in theory but freeze when they're tired. Burn the elimination grid into muscle memory - if statement 1 is sufficient, you're picking A or D, and you evaluate statement 2 just to decide between them.
Second, watch out for what I call the "one statement makes you feel clever" trap. Statement 1 gives you x = 3, you feel great. Statement 2 says x is odd - feels useless on its own. But together? Sometimes both point to the same unique value. That's answer C. People miss this because they stop thinking carefully once they've evaluated each statement alone.
Third, practice specifically with questions where the answer is E. Those are where the thinking is hardest - you need to prove that even combining both statements, you genuinely can't pin down the answer. Constructing counterexamples is the real skill, and it takes reps.
What kind of DS questions are you getting wrong - the ones where you misjudge whether one statement alone is sufficient, or the ones where you evaluate each correctly but mess up the combination?