Viewing 15 posts - 16,831 through 16,845 (of 59,101 total)
What you have to remember is, all of the costs are estimates. The only thing that ultimately matters is the actual performance.
Here's my favorite example on performance. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2016 at 10:26 pm
erouse (9/16/2016)
This is my data now.
LABORLC
152685A B C D E
152969A B
This is what I would like...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2016 at 10:02 pm
TheSQLGuru (9/16/2016)
The OP stated this database was to be promulgated to developers...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2016 at 9:59 pm
Indianrock (9/16/2016)
...but I think it's safe to say it would be considerably more difficult.
No... It's not safe to say that. As with all else having to do with computers,...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2016 at 4:47 pm
BWFC (9/16/2016)
jasona.work (9/16/2016)
Thom A (9/16/2016)
ThomasRushton (9/16/2016)
All works...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2016 at 1:52 pm
roger.plowman (9/16/2016)
This one is "convenience over security" to me, not to mention feature creep.xp_cmdshell really is a kind of a bad idea from an architectural standpoint, isn't it?
Yes... almost...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2016 at 1:21 pm
mtassin (9/16/2016)
Jeff Moden (9/16/2016)
That's certainly a part of my point, though. Why even bother disabling it? Who's going to use it when it's enable? The answer is,...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2016 at 12:56 pm
Indianrock (9/16/2016)
How so? If you meant why use powershell over xp_cmdshell ( you probably didn't mean that ), the answer would be because it has so much more functionality.
That's...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2016 at 11:43 am
Indianrock (9/16/2016)
Can we expect xp_fileExist to continue functioning? Isn't it undocumented?
Heh... Consider that you can't even rely on fully documented features to continue functioning. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2016 at 11:39 am
FrancoisFLageole (9/16/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2016 at 11:37 am
SQLNightOwl (9/16/2016)
[I agree the risk can be mitigated.
That's what I'm talking about. People think there's a risk in using xp_CmdShell and there isn't. The only risks there are...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2016 at 10:45 am
Jason Markantes (9/16/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2016 at 10:42 am
mike 62740 (9/16/2016)
Not so simple to use PowerShell from a stored procedure if xp_cmdshell is disabled... and as I said... a trade off.
You can easily create a job that uses/abuses...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2016 at 10:38 am
Indianrock (9/16/2016)
So far I only recall trying to use powershell from a sql agent job once, but this might be a better route than xp_cmdshell.
How so?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2016 at 8:14 am
mike 62740 (9/16/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2016 at 8:12 am
Viewing 15 posts - 16,831 through 16,845 (of 59,101 total)