> SQL 2000 Server.
That's too bad.
Probably the easiest is to use a function that splits the octets.
Slightly harder a function left-pads the different octets.
Another option would be to convert to an integer (remember that
you need all 32 bits, so a signed INT4 will not do).
Whether to convert on the fly, store in padded format or store in
both unpadded and padded format depends on the usage pattern.
(Can MS SQL Server do functional indexes?)
How do you intend to handle IPv6 addresses?
Jochem
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
