Viewing 15 posts - 40,846 through 40,860 (of 59,069 total)
I typically don't have a use for such a thing but, if you want feedback, submit it to the webmaster of this site as an article. You'll have to...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2009 at 8:26 pm
Ah... got it. Didn't really register on me what you were doing. Thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2009 at 8:15 pm
I can't believe that no one has answered this for you yet. I'd do it but I can't even spell SSIS. 😉 Maybe this response will act...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2009 at 8:05 pm
Be a bit careful about using character conversions of dates, folks. They're s-l-o-w. Might not make any difference with just a couple of thousand rows but if you...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2009 at 7:41 pm
Heh... absolutely... 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2009 at 7:35 pm
dmoldovan (12/2/2009)
Let me recommend some excellent resources about using arrays as input parameters:- http://www.sqlmag.com/Article/ArticleID/100657/sql_server_100657.html
- http://www.sqlmag.com/Article/ArticleID/100975/sql_server_100975.html
I just don't understand why people think they need CLR's for such...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2009 at 7:34 pm
Heh... of course most of what people use VBS and C# and Perl and... and... and... for in SSIS can many times be done in T-SQL. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2009 at 6:29 pm
On the other hand, you could do this with BULK INSERT through T-SQL without ever going near xp_CmdShell.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2009 at 6:25 pm
J-F Bergeron (12/2/2009)
Nice one Jeff,Once again, you've proven we don't need RBAR code to solve even a format problem for SQL.
Keep it up, love to learn from you,
You've made my...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2009 at 6:03 pm
Actually, I have a "splitter" method I ginned up for the removal of spaces. It's much more effective than the single character split you've included but, guess what? ...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2009 at 6:01 pm
stewsterl (12/2/2009)
Awesome! thanks.. Going to read the article tonight.
Perfect. I love it when folks strive...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2009 at 5:54 pm
Perfect... thanks for your patience. It sometimes takes me a while to sort things out especially with our combined lack of knowledge. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2009 at 5:52 pm
stewsterl (12/2/2009)
sorry. yes TOTAL_AMOUNT from the TABLE RECEIVABLE.I was using the stored procedure below but I cannot use pivot tables because our ERP system requires 2000 compatibility (80).
Heh......
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2009 at 2:13 pm
Heh.... you screw Microsoft... I'll hold your coat.:-P
I agree, though... everytime MS does an upgrade, they take away yet another useful feature or deprecate another. I don't know where...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2009 at 1:53 pm
kalyan sankar (12/2/2009)
The columns Modifier and result are not in the table,I need to create those as output.
The table only has ColumnA.
Basically given any input...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2009 at 1:48 pm
Viewing 15 posts - 40,846 through 40,860 (of 59,069 total)