a better way to convert numeric value to Hex string
CREATE PROCEDURE sp_GetHexFromNumeric
@StringID nvarchar(8) output,
declare @HEX_STRING nchar(20)
declare @HEX_CHAR char(1)
declare @Pos int
declare @TempID numeric
declare @Divisor int
set @HEX_STRING = '0123456789ABCDEF'
set @StringID = ''
set @TempID = @ID
---set @Divisor = 4096 --Support in 8 char
set @Divisor = 268435456
---if @ID > 65536
if @ID > 4294967296
set @StringID = 'FFFFFFFF'
set @Pos = @TempID/@Divisor
set @Pos =15
set @HEX_CHAR = substring(@HEX_STRING,@Pos+1,1)
set @StringID = @StringID+@HEX_CHAR
set @TempID = @TempID - @Pos*@Divisor
set @Divisor = @Divisor/16
I have always read that 8060 bytes is the maximum size. This is stated over and over again in Books Online, the MS site and numerous other sites, including this one. However a post in our forum recently questioned this. I decided to verify the problem and do a little research.
The User_Defined_Functions.exe file contains the User-Defined Functions white paper. The User-Defined functions white paper outlines the characteristics of the new user-defined function (UDF) feature that is introduced in Microsoft SQL Server 2000. The white paper also summarizes how you can create your own Transact-SQL functions to extend the programmability of Transact-SQL.
The following stored procedure will demonstrate the use of cursor metadata. Using cursor metadata we can get information about an SQL statement and use that information to dynamically generate other code such as HTML or other stored procedures.
ne of the issues you face when building Web applications is handling the errors you encounter when interacting with a back-end database. I was recently working with someone to create a new Web site with SQL Server™, ActiveX® Data Objects (ADO), and ASP. Lots of little things came up that I thought were worth sharing with MIND readers, so I'll focus this column on what I learned from this experience and the solutions to many of the problems I faced.