Viewing 15 posts - 49,591 through 49,605 (of 59,099 total)
Michael has the right idea for you helping us to help you.
In the meantime, lookup "Cross Join" in Books Online...;)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 12:29 pm
Tom Garth (6/27/2008)
There are some assumptions in what I'm about to say.
That's a heck of a good explanation, Tom...
To put it in laymen's terms, there are two ways to buy...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 12:26 pm
zxn001 (6/27/2008)
And you made me a believer, a very confused one, but still believing.
So now I'm really curious, WHY does the set loop work...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 12:19 pm
Basically, I use batch files to do the transfers like Matt suggested. You're moving files... why not let the thing that handles files the best do it... namely the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 12:12 pm
Validation of the text files should be done either during the creation of the text file, during the import of the text file, or, preferably, both.
And, yes... the copy of...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 11:56 am
To answer such a general question, I have to say lookup the following in Books Online...
Bulk Insert
BCP
BCP Format Files
Linked Servers (for text files)
OpenRowSet
DTS
SSIS
OSQL
SQLCMD
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 11:52 am
jjssilva (6/27/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 8:40 am
Matt Miller (6/27/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 8:37 am
Ummm... you think the use of a While loop is "elegant"? :blink: :Whistling:
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 8:32 am
Stephanie Giovannini (6/27/2008)
Hmmm... I suppose the second table is the best way to do it, if I'm allowed to do so. At least I now have ammunition.
Sorry, Stephanie... I have...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 8:30 am
TheSQLGuru (6/27/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 8:09 am
jcrawf02 (6/27/2008)
Sergiy (6/27/2008)
jcrawf02,can you explain this:
ISNULL(count(distinct #PLANDATA_Claim.claimid),0) AS "FFS",What ISNULL is doing here?
I have...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 8:07 am
jcrawf02 (6/27/2008)
Sorry, didn't use that in this example. What I ended up doing in my live version is this:LEFT JOIN #member ON (ISNULL(PLANDATA_Claim.enrollid,ENCOUNTER_Claim.enrollid) = #member.enrollid )
Hmmmm.... I suppose that...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 8:05 am
Thanks for the feedback...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 8:00 am
Heh... wasn't me, Bill... I'm still trying stuff out...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 7:54 am
Viewing 15 posts - 49,591 through 49,605 (of 59,099 total)