Viewing 15 posts - 31,351 through 31,365 (of 59,101 total)
Chad Crawford (1/25/2012)
Evil Kraig F (1/24/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 6:37 pm
Brandie Tarvin (1/25/2012)
Anyone can fly. You just throw yourself at the ground and miss.
BWWWAAAA-HAAAAAA-HAAAAA!!!! Now THAT's funny!!! Major T-Shirt material there, Brandie! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 6:35 pm
Steve Jones - SSC Editor (1/25/2012)
SQL Kiwi (1/24/2012)
Steve Jones - SSC Editor (1/24/2012)
But you can ski?
I tried snowboarding once (in a supervised inside environment[/url]) and that was enough to convince...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 6:31 pm
Apologies for the distraction from "Charmer's" questions... I just want to say "thanks" to Craig and Matt for the feedback on my question.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 6:25 pm
Agh... My apologies. The reason I didn't offer up any code is because it would appear that Francesc has sussed this problem and I meant to say so.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 6:19 pm
babatmanpub (1/25/2012)
Just for those who would like to change $pshome : you can do it here :with regedit
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PSConfigurationProviders\Microsoft.PowerShell]
"ApplicationBase"="c:\\Windows\\System32\\WindowsPowerShell\\v1.0"
Nicely done.
Shifting gears a bit (and no implications about the code...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 6:17 pm
Hmmm... I haven't tried it but I wonder if using a synonyn for the remote table would work in this case.
Also, is the function being used alone? (Probably not). ...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 6:08 pm
You know... that's probably the only thing I haven't tried. I'll give it a whirl when I get back to work tomorrow. Thanks, Brandie.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 6:03 pm
I've not been able to find a solution for this other than someone saying that the problem doesn't occur if you use the deprecated SysMail. I guess the work...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 6:23 am
phil.walter 85406 (1/24/2012)
simply REPLACE([FIELD NAME],',','')
It won't work for the third example the OP gave where the comma between two items must be preserved.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 6:16 am
SQLKnowItAll (1/23/2012)
SQLKicksButt (1/23/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 23, 2012 at 7:43 pm
KWymore (1/23/2012)
Good question. Made me look up BOL as I had never thought to use Resource Governor that way.
BWAA-HAAA!!! The only "Resource Governor" that I use is denial of...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 23, 2012 at 7:30 pm
I have to ask... is a FOREACH loop in SSIS going to be as effecient as creating a result set in a stored procedure that uses FOR XML PATH() and...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 23, 2012 at 7:20 pm
SQLKnowItAll (1/23/2012)
Is EXECUTE AS not an option?
It might not be an option if you've written a nice, high performance, inline Table Valued Function.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 23, 2012 at 7:17 pm
Charmer (1/23/2012)
i have a column having some records like ",Clayton" and "Township," and "Clayton, Dept" ...
i want to remove unnecessary commas which is presented in...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 23, 2012 at 6:41 am
Viewing 15 posts - 31,351 through 31,365 (of 59,101 total)