Please start any new threads on our new site at http://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 SQL Server 2000 - Unsigned Integers
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

AskSQLTeam
Ask SQLTeam Question

USA
0 Posts

Posted - 12/05/2006 :  07:28:34  Show Profile  Visit AskSQLTeam's Homepage  Reply with Quote
Dustin writes "What would you consider to be the best practice to use an unsigned 32-bit integer? For our application we need several 32-bit unsigned integers and I would hate to use a bigint just for a 32-bit field. Even a binary(4) require a 4 byte overhead which is just as bad as a bigint (8 bytes of storage). Thanks for your help.

SQL Server 2000"

SwePeso
Patron Saint of Lost Yaks

Sweden
30421 Posts

Posted - 12/05/2006 :  07:38:19  Show Profile  Visit SwePeso's Homepage  Reply with Quote
Why can't you use SIGNED 32-bit integer?
Are you doing some bit operations?


Peter Larsson
Helsingborg, Sweden
Go to Top of Page
  Previous Topic Topic Next Topic  
 Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.03 seconds. Powered By: Snitz Forums 2000