Viewing 15 posts - 48,301 through 48,315 (of 59,099 total)
Great info! I gotta try it. Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2008 at 11:28 pm
Cool! I'd guessed wrong. ColumnC in the orginal code wasn't prefixed by a table alias and I'd guessed it was in Table1. Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2008 at 11:25 pm
Ummm... all those bloody REPLACE's are gonna be slow. I just thought of another way using our friends the Tally table and the "quirky update". It'll take me...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2008 at 11:21 pm
Heh... yeah, I wouldn't want to take a call in the middle of a cold one, either.
Split functions always work, especially on a single delimiter. Obviously, your stuff has...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2008 at 11:00 pm
BTW... as you already know, the rows you originally posted import just fine because they are, despite appearances, properly formatted CSV's. The delimiters also line up and could be...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2008 at 10:37 pm
You want the rows you posted to be split instead of imported?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2008 at 10:31 pm
Heh... understood... and I frequently do the same thing if the file is crap...
... but that's not what you asked.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2008 at 9:22 pm
Dave (9/15/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2008 at 9:19 pm
I found the URL I was thinking about.
http://sqlblog.com/blogs/hugo_kornelis/archive/2008/03/10/lets-deprecate-update-from.aspx
I disagree with just about everything he says there. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2008 at 8:30 pm
Sorry for the delay...
Absolutely the easiest way to read a "properly formed" CSV file is using OpenRowSet. If the file is called "ImportTest.csv" and it's stored in "C:\Temp", and...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2008 at 8:23 pm
Pam Brisjar (9/15/2008)
Hey Jeff - Just wanted to say I've been using your RBAR acronym in my interviews. It really gets the point across.
Glad it helps, Pam. Thanks...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2008 at 6:17 pm
Think of spt_Values as a "config" table for SQL Server. I just happen to know that there's a set of sequential numbers from 0 to 2047 in SQL Server...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2008 at 6:07 pm
Marios Philippopoulos (9/14/2008)
Jeff Moden (9/14/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2008 at 5:59 pm
dulanjan (9/15/2008)
so yeah if you put in any consecutive saturday and sunday you get...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2008 at 5:57 pm
jmuldoon (9/15/2008)
Heh... imagine this... there are some folks that think the FROM clause in an UPDATE is a bad thing.
I would be interested in hearing any argument(s)...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2008 at 5:49 pm
Viewing 15 posts - 48,301 through 48,315 (of 59,099 total)