Implicit and explicit castings results in a bad plan - response (1) by VBurmist

Hi, 
the castings - both implicit and explicit - are consuming CPU that is not necessary.  Therefore, it is a good idea to design the physical database model to minimize the castings.    
In the example above - if the field really contains only integers, then the data type should be defined as integer.  If only some values are integer (only for certain rows), then the data modeller might want to add an additional integer field for that data.
Regards,
Vlad.