Viewing 15 posts - 39,526 through 39,540 (of 59,072 total)
{edit} Never mind... misread the post...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 9:21 pm
Nikki-395727 (3/2/2010)
I knew that this is the best I can do with the current set up but wanted to confirm.
I just feel bad that all our...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 9:06 pm
Paul White (3/3/2010)
For general advice, and a solid methodology that works, read This Microsoft White Paper.
BWAA-HAAA!!! 😛 The very first item in the "Common scenarios to avoid in OLTP"...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 8:57 pm
dakshinamurthy-655138 (3/1/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 8:50 pm
Roust_m (3/2/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 8:37 pm
Ah... one final note. If you can live within the bounds of VARBINARY(8000) and change the input parameter datatype from VARCHAR(MAX) to VARCHAR(8000), then you'll get roughly 3 times...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 8:34 pm
Relatively short test (15k conversions of NEWID()) on my box came in at about 5 seconds on an 8 year old p4 1.8GHz... should do a lot better on your...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 8:30 pm
I forgot to mention that if you don't know what a Tally table is (CTE in this case) or how it works to replace certain While Loops, please read the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 8:19 pm
Never mind... decided to make a "direct" replacement so you don't necessarily have to change code. Read the comment in the code header below...
CREATE FUNCTION dbo.fn_varbintohexstr
/*****************************************************************************************
Purpose:
...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 8:17 pm
Roust_m (3/1/2010)
A developer approached me in regards for sys.fn_varbintohexstr function they are using at the moment saying it is slow in production: 60 seconds for 15k records (though fast...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 7:33 pm
Paul White (3/2/2010)
http://florianreischl.blogspot.com/2009_09_01_archive.html
It covers all the main methods, including WHILE loops, Tally tables, XML, and...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 6:58 am
Heh... you really really don't won't to use even well written While Loops for this though.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 6:28 am
lmu92 (3/1/2010)
Jeff Moden (3/1/2010)
I know you know this, Lutz... just saying this in case anyone thinks otherwise....
Don't rely on the execution plan for differenences in performance either. Sure,...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 6:12 am
mstjean (3/2/2010)
Jeff Moden (3/1/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 5:56 am
Mohamed Asane (3/3/2010)
DECLARE @data NVARCHAR(MAX),
@delimiter NVARCHAR(5)
SELECT @data = '1,2,3,6,7,8,R,a,n,g,a,n,a,t,h',@delimiter = ','
DECLARE @textXML XML;
SELECT @textXML = CAST('<d>' + REPLACE(@data, @delimiter, '</d><d>') + '</d>' AS XML);
SELECT...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 5:50 am
Viewing 15 posts - 39,526 through 39,540 (of 59,072 total)