Everyone is talking about Coverage Driven Verification and everyone wants go random. Randomization leads to requirement for constrained transactions. Considering couple of common tit bits; ensures that constraints are written properly and behave as we intend them to; without overloading the constraint solver. This saves the critical time during coverage closure and helps to cut the time tools constraint solver consumes. This paper explains simple considerations for commonly used SystemVerilog constraints.