Viewing 15 posts - 33,856 through 33,870 (of 59,102 total)
Lowell (5/25/2011)
the columns in the table and the columns in the BULK insert must match exactly, with no extra or missing columns....unless you use a format file.
As a possible alternative...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 25, 2011 at 10:28 am
fahey.jonathan (5/25/2011)
Is there a reason why you chose a VARCHAR(8000) instead of a VARCHAR(MAX)? I modified the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 25, 2011 at 10:24 am
ChrisM@home (5/25/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 25, 2011 at 6:43 am
Gianluca Sartori (5/25/2011)
MaybeProbably I'm short-sighted and I don't understand exactly what you mean.Can you give us a small example?
Yes, I believe I can. And I believe it...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 25, 2011 at 6:41 am
aphillippe (5/25/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 25, 2011 at 6:34 am
Jeff Moden (5/24/2011)
This can be done quite simply using REPLACE, a single concatenation, and a WHERE clause with a LIKE. Give it a try. 😉
How embarrassing. I "missed"...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 25, 2011 at 5:59 am
Lowell (5/25/2011)
Jeff Moden (5/24/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 25, 2011 at 5:55 am
I do it more often than not. Peter Larsson calls the process "pre-aggregation". You've seen me refer to it as "Divide'n'Conquer" methods. I do it for performance...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 25, 2011 at 12:24 am
Gosh... I've seen this type of conversation come up over and over and people still haven't sussed it.
[font="Arial Black"]From the article[/font]
--Jeff Moden
Change is inevitable... Change for the better is not.
May 25, 2011 at 12:08 am
vradul (5/24/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 24, 2011 at 11:09 pm
Gosh, folks. I've not tried to import the data (yet) but the "Read Me" pointed out in the original posts seems to identify column requirements quite nicely. I've...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 24, 2011 at 11:02 pm
You CAN use a sequence table but not quite the way you have it. You don't need to do an insert/delete... you can do an UPDATE using the well...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 24, 2011 at 10:52 pm
sqlnaive (5/24/2011)
Unfortunately that brings me to the same point where I started. In a complex stored procedure, what should be the thumb rule for implementing temporary data [records upto 800].
That's...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 24, 2011 at 10:21 am
Nadrek (5/23/2011)
Jeff Moden (5/22/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2011 at 9:12 am
mister.magoo (5/23/2011)
Jeff Moden (5/23/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2011 at 2:59 am
Viewing 15 posts - 33,856 through 33,870 (of 59,102 total)