Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
deepa
Starting Member
17 Posts |
Posted - 2002-02-11 : 23:43:54
|
| I have a column named calleid in my database which will have afixed length of 47.It is possible to give the data type as char or binary. What I need to know is which datatype is optimal 'coz I will be using this Callid in most of the queriesI need to know whether char or binary datatype is feasible for query performance.Deepa |
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2002-02-11 : 23:58:00
|
| That really depends on what data you want to store in it.Damian |
 |
|
|
fisherman_jake
Slave to the Almighty Yak
159 Posts |
Posted - 2002-02-12 : 00:33:00
|
Yeah, I even had a read from BOL: quote: Using Binary DataThe binary and varbinary data types store strings of bits. Although character data is interpreted based on the Microsoft® SQL Server™ code page, binary and varbinary data is simply a stream of bits. binary and varbinary data can be up to 8,000 bytes long.Binary constants have a leading 0x (a zero and the lowercase letter x) followed by the hexadecimal representation of the bit pattern. For example, 0x2A specifies the hexadecimal value of 2A, which is equivalent to a decimal value of 42 or a one-byte bit pattern of 00101010.Use binary data when storing hexadecimal values such as a security identification number (SID), a GUID (using the uniqueidentifier data type), or a complex number that can be stored using hexadecimal shorthand.
==================================================Do not argue with IDIOTS. They will take you down to their level and BEAT you with experience.Master Fisherman |
 |
|
|
|
|
|