Char datatype doesn't support unicode. Use Nchar in your temp table instead.

That aside, I don't see anything unusual going on at rows 5136 & 5138.


Robert Davis


-----Original Message-----
From: Juan Vera [mailto:mssqldba-ezmlmshield-x46454167.[Email address protected]
Sent: Monday, October 31, 2005 9:44 AM
To: LazyDBA Discussion
Subject: Extreme Discomfort...

Can someone run the snippet below (in Q/A in grid mode) and explain what happens between rows 5136 & 5138 of the result set, if anything?

Best,

Juan Cristián

/******************/

create table #unicode([#] smallint, [unicode] char(1))

declare @i int

select @i = 0
while @i < 32000
begin
insert into #unicode
select
@i as [#]
,nchar(@i) as [unicode]

select @i = @i + 1
end

select * from #unicode

drop table #unicode


---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY Website : http://www.LazyDBA.com To unsubscribe: http://www.lazydba.com/unsubscribe.html


MS Sql Server LazyDBA home page