erm...I am not sure if I understand what you mean? The whole principle of a datatype is to manage data of a particular type....for instance, if you are dealing with a boolean value then you should use a bit (though you could use an integer if you wanted to). For text you should use Varchar or Text depending on amount and type of data you are storing.
I have never really been in a situation where I have NEVER had to use a datatype for any reason other than it would not represent my data. HTH Neil -----Original Message----- From: Michael Hodgdon [mailto:[EMAIL PROTECTED] Sent: None To: CF-Talk Subject: WOT: SQL Data types I am curious how religiously people stay true to using data types for MS SQL Server. I know some of these stretch to other RDBMS's, however, I would like to know what people in industry think. What type of general rules of thumb do people follow when planning data types for a data store? For instance Money, Numeric, varchar, int, bigint ... I think you get the point. I am looking for response such as; never use that type, it won't convert to Oracle. Never use that type, the space you save is not worth it, etc.... If this needs more elaboration, please let me know Mike. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/lists.cfm?link=t:4 Subscription: http://www.houseoffusion.com/lists.cfm?link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm
