Viewing 15 posts - 33,691 through 33,705 (of 59,099 total)
Shawn Melton (6/13/2011)
I tend to use SQLCMD (that is if PowerShell is not available to me :-D). We disable access and use of xp_cmdshell.
Understood. Thanks for the feedback.
What do...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2011 at 9:57 am
GSquared (6/13/2011)
Of course, turning on CLR has its own security issues, but they can be mitigated more effectively.
That's interesting. Thanks, Gus. You mention more effective mitigation of security...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2011 at 9:55 am
sql_jr (6/13/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2011 at 9:51 am
I guess this has all been a misunderstanding. So far as I'm concerned, we proved the original post wasn't going to do a thing for you. I posted...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2011 at 9:43 am
taybre (6/13/2011)
Hi Jeff,Thank you so much for your post. I did some modifying but you code work PERFECTLY. Thanks again
:-):-):-)
Wow. Old post, too. Thank you very much for...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2011 at 8:16 am
MyDoggieJessie (6/13/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2011 at 8:13 am
BWAA-HAAA!!!! 48 reads and 2-1/2 days later and no one has a compelling reason to use xp_CmdShell? Considering the number of posts asking how to use it, I'm really...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2011 at 7:54 am
Matjaz Justin (6/13/2011)
select N2.n as dan, N.n - 1 as Ura, isnull(sum(SaleQTY), 0) as D
from dbo.GetNums(24) as N cross join dbo.GetNums(31) as N2
left join...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2011 at 7:01 am
Folks, the GetNums function that Matjaz reference is Itzik Ben-Gan's cascading Cross Join code wrapped in a function. If you decide to use that instead of some other method, make...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2011 at 6:41 am
harry9katz (6/13/2011)
HiCan use cross-join with hour table
This is easier solution by more costly on the execution plan
Cool! Got code? 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2011 at 6:31 am
Matjaz Justin (6/13/2011)
select N2.n as dan, N.n - 1 as Ura, isnull(sum(SaleQTY), 0) as D
from dbo.GetNums(24) as N cross join dbo.GetNums(31) as N2
left join...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2011 at 6:29 am
p.s. I guess todays caffeine has finally failed me. You had the following near the bottom of one of your posts. What does it mean?
Oh and, /hijack...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2011 at 10:58 pm
Daaannnggg.... 😀 Sounds almost like what I'd write except the "block code" setting slows me down. 😛 Nicely done.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2011 at 10:53 pm
allmhuran (6/12/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2011 at 10:41 pm
allmhuran (6/12/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2011 at 10:33 pm
Viewing 15 posts - 33,691 through 33,705 (of 59,099 total)