Viewing 15 posts - 43,921 through 43,935 (of 59,063 total)
Phil Factor (5/2/2009)
but I hit problems with the UPDATE ... FROM query, whist using variables. SQL Server Bugs, I'm afraid.
Which bugs?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 11:15 am
m.berggren (5/2/2009)
Maybe there is something wrong when I create the table...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 10:59 am
john.arnott (5/2/2009)
Sorry for any confusion; I'm not the original poster. He posted in the SQL 2000 forum with just a snippet of code -- no table def's, nothing to...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 10:55 am
Any feedback on this, Jim?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2009 at 9:32 pm
john.arnott (4/30/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2009 at 9:25 pm
m.berggren (4/30/2009)
Jeff:How does this so called "anchor" field works ?
Here are a helpful link about statements in SQL Anywhere Studio 9.0.2
http://www.ianywhere.com/developer/product_manuals/sqlanywhere/0902/en/html/index.html
Regards
Magnus
Matt Miller did some testing and claimed that without it,...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2009 at 9:20 pm
john.arnott (4/30/2009)
But this is SQL 2000.....
I thought you said you were using SyBase.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2009 at 9:17 pm
Doc (4/30/2009)
A funny side of Outsourcing from Onion news network 😀http://www.theonion.com/content/video/more_american_workers_outsourcing
THAT's freakin' funny, Doc! Heh... I'll bet there are folks out there that have actually managed to pull...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2009 at 9:05 pm
Actually, it's a "white space" problem.
[font="Courier New"]DECLARE @CrLf NVARCHAR(MAX)
SET @CrLf = 'X '+CHAR(13)+CHAR(10)
SELECT LEN(@CrLf),
LEN(REPLACE(@CrLf,CHAR(13)+CHAR(10),''))[/font]
Any sproc that has spaces just before the last CrLf will have the problem because when the trailing CrLf goes away, those spaces become...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2009 at 8:43 pm
See what I mean? This works...
[font="Courier New"] SELECT [Name],LenCount,LenTally,REPLACE(definition,CHAR(13)+CHAR(10),CHAR(1))
FROM (
SELECT TOP(200) o.name, m.definition,
(DATALENGTH(m.Definition)-DATALENGTH(REPLACE(m.Definition,(CHAR(13)+CHAR(10)),'')))/4 AS LenCount,
(
SELECT COUNT(*) AS DoDah
FROM Tally
WHERE N <= LEN(definition)
AND SUBSTRING(definition,N,2) = CHAR(13)+CHAR(10)
)AS LenTally
FROM MASTER.sys.all_objects o
JOIN MASTER.sys.all_sql_modules m ON o.OBJECT_ID = m.OBJECT_ID
WHERE TYPE = 'P'
)d
WHERE LenCount LenTally[/font]
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2009 at 8:04 pm
Phil Factor (5/1/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2009 at 7:58 pm
Paul White (5/1/2009)
I have *just* realized the point of Lynn's solution!
It avoids the I/O on the custom tally table completely.
Not my finest moment.
Luckily it won't be available on...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2009 at 7:02 pm
I still want to know what the CLR procedure is going to do. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2009 at 6:52 pm
Phil Factor (5/1/2009)
...but their developers seem unable to fix things so they work like they used to.
Ouch.
They're doing all they can to put in a better solution ASAP. The problem...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2009 at 12:03 pm
Florian Reischl (5/1/2009)
TheSQLGuru (5/1/2009)
Flo, are you getting your reads from SET STATISTICS IO ON? IIRC UDFs don't report IO correctly in this manner. Try getting them with Profiler.
Good...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2009 at 11:14 am
Viewing 15 posts - 43,921 through 43,935 (of 59,063 total)