Viewing 15 posts - 34,756 through 34,770 (of 59,099 total)
Kiara (3/7/2011)
But... but... it's *pretty*! I just wanted to look at it... really! We have such *boring* money over here in the States...
-Ki
BWAA-HAA!!! I will be happy to take...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2011 at 6:02 pm
jim Etheridge (3/7/2011)
The rtrim/ltrim function apparently removes the unprintable xml tokens, and the substring removes the first comma. This works...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2011 at 5:04 pm
SQLkiwi (3/7/2011)
Jeff Moden (3/7/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2011 at 5:02 pm
varunkum (3/7/2011)
Please see the image above i want the output like this. I hope i made myself clear. I just need an idea to print all the codes even if...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2011 at 9:49 am
"Accidental Cross Join" and Many-to-Many join
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2011 at 9:45 am
Never mind on the .WRITE method. I just found the answer in Flo's article that you provided a link for. Thanks for the link.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2011 at 8:34 am
TheSQLGuru (3/7/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2011 at 8:23 am
SQLkiwi (3/7/2011)[hrWell it's not really RBAR - it is a set-based solution of sorts, but you are absolutely right to point out that it is not at all suitable for...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2011 at 8:21 am
There are ways to build all 200 commands at once and then execute them with a single EXEC but it won't make the code any more effecient because building the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2011 at 6:33 am
Nah... no pork chops required on this friendly little thread. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2011 at 6:23 am
Phil Factor (3/7/2011)
I just had a look at the projects I'm using Powershell for and there is nothing there that SSIS can be made to do.
Now THAT's an interesting thought....
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2011 at 6:21 am
Saravanan Durairajan (3/6/2011)
Why do I need Powershell, when I can do all the stuff in GUI using SSIS? Powershell is another geek tool.
Heh... because some of us are heavy-duty batch...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2011 at 6:20 am
Mike01 (3/6/2011)
don't forget the where clause or all of your records will be the same 😉
Thanks for the catch, Mike. Shamefully, I only fixed what I saw. :blush:
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2011 at 6:16 am
guruprasat85 (3/7/2011)
Declare @var varchar(1000)Set @var=''
Select @var = @var + fruit + ',' from #temp
Select substring(@var,1,len(@var)-1)
Please read the posts above for why that's a bad idea and what to do about...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2011 at 6:14 am
Mad-Dog (3/6/2011)
I've 2 server with the same tables and i need to move data between the DEV to the PROD.
my question is how i can write the tsql that will...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2011 at 1:19 pm
Viewing 15 posts - 34,756 through 34,770 (of 59,099 total)