Re: Performance

Umesh Bellur (bumesh@torpedo.tcs.com) wrote: > I'd like to know the performance issues of storing 64 bits as a > character string Vs storing them as 2 long integers. Thanks in advance > for all replies. What does the "64 bits" represent? Is it a "long long"? Is it 8 characters? Is it a "double"? From a performance perspective, a char(8) is slightly "better", as your 64-bit entity resides in a single row. Storing the entity as 2 long integers costs you two columns: twice the logical I/O's, although probably the identical number of physical I/O's. A better approach is to make a data type that maps to char(8). Make all your references to that column in terms of that data type. This becomes especially useful if the type you're representing is something like a "long long". Once Sybase supports "long long" natively (hint, hint), you can transparently change the schema. -- -- Eric William Burger -- +1 301/417-0700(v) 0707(f) -- -- George Mason University -- SITE PhD Program -- -- The Telephone Connection -- Director of Engineering -- The views expressed above do not necessarily reflect the views of George Mason University or The Telephone Connection.