Viewing 15 posts - 41,461 through 41,475 (of 59,067 total)
SALIM ALI (6/18/2009)
declare @string varchar(50)
SET @string = 'ABCDEFGHIJ123'
select reverse ( substring ( reverse ( @string ) , 1 , 3 )...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2009 at 7:30 pm
Piotr.Rodak (10/18/2009)
To hire and to consider hiring are two different things Jeff 😉
Heh... one is a waste of time and effort without the other and both are a waste of...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2009 at 7:27 pm
Also, I know it's unnatural, but for the best accuracy, multiply by 100 first, then divide. If you do that, them use 100.0 instead of just 100 and you'll...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2009 at 7:22 pm
robertm-772679 (10/18/2009)
The numbers were just used as an example. I'm really using integer fields as part of the equation and your right, I did not have to...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2009 at 7:21 pm
I'm not sure that BULK INSERT supports the DATE datatype. I've not been able to find any documentation one way or the other.
Shifting gears a bit... my recommendation is...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2009 at 7:18 pm
I'm a bit surprised that you could add a column without getting an error about the table being replicated.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2009 at 7:04 pm
bitbucket-25253 (10/18/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2009 at 6:50 pm
Gift Peddie's good post brings up a real sore spot with me... why does everyone think that the Agile Manifesto says "[font="Arial Black"]No[/font] Documentation" whatsoever? Why does everyone think...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2009 at 6:38 pm
"Yes" or "No" are the wrong answers... for the information given in the original post, the correct answer is "It Depends"... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2009 at 6:25 pm
Jeffrey Williams-493691 (10/18/2009)
Jeff - without knowing which SAN it was, it's hard to say what is actually possible.
Heh... Agreed... Everything is impossible if you don't know what the possibilities are....
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2009 at 6:13 pm
Steve Jones - Editor (10/18/2009)
Or maybe they've changed the rules now that Jeff isn't serving :-D:-P:w00t:
Heh... I have been known to have that effect on people. Pork chops anyone?...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2009 at 6:08 pm
I believe the SAN snapshots we were doing operated kind of like transactional replication where the "clone" was always kept up to date in a parallel fashion. The production...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2009 at 10:49 am
talltop-969015 (10/17/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2009 at 10:45 am
And here's a function for items that don't exceed 8K...
--===== Create a function that uses VARCHAR(8000) with a DUPE Eliminator
CREATE FUNCTION dbo.Concat8KTestDupElim
...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2009 at 10:14 am
Min-437192 (10/18/2009)
Yours is pretty cool, but what do I need to modify if I want to get rid of duplicates? 🙂
Here's one way that will handle the VARCHAR(MAX)...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2009 at 10:04 am
Viewing 15 posts - 41,461 through 41,475 (of 59,067 total)