Viewing 15 posts - 52,396 through 52,410 (of 59,098 total)
Hoo boy... I understand... 2,134 columns of CSV data is enough to make anyone cranky.
How "clean" is the input file? Any problems with missing delimiters, etc?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 23, 2008 at 12:59 pm
Ok folks... the statement level OPTION (RECOMPILE) that Matt spoke of really did the trick both on this current problem and the previous problems I had. Estimated execution plan...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 23, 2008 at 12:44 pm
Jeff Moden (2/23/2008)
matt stockham (2/23/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 23, 2008 at 11:22 am
GilaMonster (2/23/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 23, 2008 at 11:15 am
matt stockham (2/23/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 23, 2008 at 11:12 am
Not 100% sure, but I think it's just a problem with permissions. What login is the agent using and does it have the privs to see the same directories...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2008 at 8:59 pm
MD (2/22/2008)
I can't use bulk insert because of course the flat file does not match the table structure.
If you use a BCP format file, you can. 😉 See BOL...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2008 at 8:45 pm
Thanks for the feedback guys...
Ryan and Mike C... thanks for the performance comparisons. That's good stuff. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2008 at 8:19 pm
Heh... sorry about that, Matt. Thanks for the help...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2008 at 7:19 pm
Understood... but this doesn't even have anything to do with indexing... changing a constant to a variable causes a massively detrimental change in the execution plan. This is a...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2008 at 3:25 pm
Well, good! At least it's not just me! 😀 Thanks for the help, Matt and Michael.
I also ran into this the other night on something totally different...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2008 at 1:29 pm
Oh yeah... and, of course, it works just fine. But, any idea on how to make it work without being dynamic though? Seems the optimizer is making a...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2008 at 12:36 pm
Edward (2/22/2008)
have a look at thishttp://ryanfarley.com/blog/archive/2004/03/01/390.aspx
Hope it helps
Pretty good explanation of SET vs SELECT... horrible method of creating a split function. Use a Tally table, instead.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2008 at 6:36 am
1. I just have modified my select statement a bit like iam just taking all now
means...
bcp "Select * from CurveTempDB.dbo.tLoanVectors where cusip='86359B6G1' " queryout C:\Sample.txt -T -c
for which am still...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2008 at 6:31 am
VALEK (2/21/2008)
It would be great if...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2008 at 5:44 am
Viewing 15 posts - 52,396 through 52,410 (of 59,098 total)