Viewing 15 posts - 40,576 through 40,590 (of 59,072 total)
I agree... the problem with that is (IIRC) that xp_getfiledetails is no longer available in SQL Server 2008 (although xp_DirTree is) so any upgrade plans would make some pretty loud...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2009 at 10:41 am
Provided that "value" and "some value" are different in your example, this is easy...
DECLARE @Col1 somedatatype
UPDATE yourtable
SET @Col1 = Col1 = value,
...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2009 at 10:16 am
Heh... I notice you have a "name splitter" in the code. Let me ask, what are you going to do with a name like Dr. Robert Douglas van Guttenburg...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2009 at 10:12 am
First of all, I have to remind everyone that SQL Server isn't a word processor and storing formatted text numbers is very contrary to what SQL Server should be used...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2009 at 10:03 am
guarddata (5/19/2003)
If you have
DECLARE @numStr
SET @numStr = '345.2300'
then
SELECT @numStr = REPLACE( RTRIM( REPLACE(...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2009 at 9:03 am
Never mind... wrong rev...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2009 at 8:54 am
First of all, if the table will really have 3,000 columns, then the choice of having such a wide table simply vanishes because SQL Server can only have something like...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2009 at 8:34 am
Heh... I just bought an HP "GS" series with a 17.1" screen and a full size keyboard that has a real live separate numeric keybad. Netbook would kill me...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2009 at 8:04 pm
Step 1 to a high speed T-SQL solution that does NOT require xp_CmdShell... try the following command and see if you understand the output....
EXEC Master.dbo.xp_Dirtree 'C:\',1,1
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2009 at 7:49 pm
purushotham.k9 (12/17/2009)
yes..60 days of data on day wise and i am using SQL server 2005
Please see the following... it'll do what you want. You will have to spend a...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2009 at 7:43 pm
Lookup STUFF in Books Online... that should do it for you. And, no... not being a smart alec here... there is an SQL Function called "STUFF".
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2009 at 7:39 pm
Same as Jason, here. Working both weeks with a couple of days off in the later.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2009 at 7:38 pm
Sorry for my apparent absence, but I didn't want to put any kind of a slant on the possible responses.
I have to admit a great amount of surprise at the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2009 at 7:09 pm
Actually, thank you. Lot's of people just want to be spoonfed instead of taking the time to spend a bit of time with BOL. It's a pleasure to...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2009 at 6:25 pm
Jack Corbett (12/18/2009)
Msg 241, Level 16, State 1, Line 12
Conversion failed when converting date...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2009 at 4:46 pm
Viewing 15 posts - 40,576 through 40,590 (of 59,072 total)