Viewing 15 posts - 55,426 through 55,440 (of 59,098 total)
Heh... but it IS documented in the SQL Specifications...
| Columns per base table | 1,024 | 1,024 |
Why would BCP support more than that? ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 11, 2007 at 8:39 pm
Must be...
EXEC (@Cmd)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 11, 2007 at 8:33 pm
I noticed that the growth rate is set to 10%. At the current size, that means that then next growth will be approximately 16 gig... that will take quite a...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 11, 2007 at 8:33 am
I believe what you're looking for is a kind of "histogram". The other solutions are great but if there are any unexpected characters, the cross-tabs will miss them and, if...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2007 at 7:40 pm
Have had similar problems in the past and have found it quicker to re-export the desired rows and re-import them using the parsing of Bulk Insert or BCP.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2007 at 6:36 pm
Post the code, Will...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2007 at 6:32 pm
Hey, Phil...
I just went back and read my reply about testing it... it sounds a lot sarcastic and I didn't mean to make it sound that way. Hope you took...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2007 at 6:25 pm
Ya beat me to it, John. ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2007 at 6:22 pm
Now, there's some common sense thinking outside the box... thanks, Lowell. ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2007 at 6:20 pm
No, no... he's not miffed... it's a bit of a language barrier thing and, because of that, he comes off as being short... He's really trying to help you think...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2007 at 6:18 pm
Thanks, Lynn...
Heh... I don't have 2k5, either... was going on someone else's word... thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2007 at 11:27 am
Just additional info... Foreign Keys must reference either a PK or a column with a UNIQUE index... that not-with-standing, you still can't reference a computed column as a Foreign Key...
--Jeff Moden Change is inevitable... Change for the better is not.
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)
August 10, 2007 at 10:26 am
| I have a table which contains a date field which is a string with format 'yyyymmdd' ... |
It's almost...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2007 at 8:23 am
I don't think so... foreign keys don't automatically make indexes like Primary Keys do. They make excellent candidates for indexes, though.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2007 at 7:59 am
Pretty sure "OR" can't be used here....
SELECT CASE RowNum
WHEN 1 OR 10 THEN '1 or 10'
ELSE 'Not 1 or 10'
END
FROM jbmTest
WHERE RowNum <=10
Server: Msg...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2007 at 7:50 am
Viewing 15 posts - 55,426 through 55,440 (of 59,098 total)