Viewing 15 posts - 25,351 through 25,365 (of 59,099 total)
nutty (11/21/2013)
However the trouble is, these child codes are common codes for various other parent codes.
For example two different parents can share...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2013 at 2:36 pm
Steve Jones - SSC Editor (11/21/2013)
Jeff Moden (11/20/2013)
The article link in the post above doesn't work. It takes me to a "Not found" window.
Do you mean the URL to...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2013 at 2:31 pm
opc.three (11/20/2013)
And the sysadmin members? ...oh that's right, you argue that you must trust them implicitly.
Jeez, Orlando. If you can't trust an SQL Server Admin or a Windows Admin...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2013 at 8:27 am
That's just it. There are no security challenges to it. I don't allow users to use xp_CmdShell directly. I don't allow apps to execute it directly (never...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2013 at 10:52 pm
opc.three (11/20/2013)
Jeff Moden (11/20/2013)
opc.three (11/20/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2013 at 10:36 pm
opc.three (11/20/2013)
Chances are I could accomplish this through a SQLCLR. I could definitely setup an Agent job that a low-priv user could run by executing a stored proc.
Heh... who...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2013 at 10:29 pm
The article link in the post above doesn't work. It takes me to a "Not found" window.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2013 at 10:11 pm
opc.three (11/20/2013)
I can think of ways a non-SA...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2013 at 9:50 pm
nutty (11/20/2013)
I have a data where there are parent and child product.
Each parent has got a unique code(P1) and a link code (L1) on their account
and each...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2013 at 9:03 pm
jend (11/20/2013)
CREATE TABLE [dbo].[ITEM_SUPERSESSION](
[Superseeded_Item] [char](15) NOT NULL,
[Superseeding_Item] [char](15) NOT NULL,
CONSTRAINT [PK_ITEM_SUPERSESSION] PRIMARY KEY CLUSTERED...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2013 at 8:36 pm
opc.three (11/20/2013)
Jeff Moden (11/20/2013)
opc.three (11/19/2013)
Jeff Moden (11/5/2013)
SQLRNNR (11/5/2013)
Jeff Moden (11/5/2013)
Heh... I had to think about it. For me, the correct answer would have started with "Exec xp_CmdShell". 😀not sp_configure??
:w00t::-D
Heck...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2013 at 5:52 pm
Heh... I remember some of the original computer games. If you can't move left, right, forward, back, up, or down, then change color!
Add a persisted computed column to the...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2013 at 4:31 pm
You could maintain some semblence of the meta-date for each "element" by using SQL_Variant for this.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2013 at 4:11 pm
This is a very good example of why you should (and I don't use the word often) ALWAYS use the two part naming convention. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2013 at 4:03 pm
nutty (11/20/2013)
Thanks for this.I am working in pl/sql and it says 'LEFT' as an invalid identifier
Change the LEFT to a SUBSTRING starting at 1 with a length the same...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2013 at 4:01 pm
Viewing 15 posts - 25,351 through 25,365 (of 59,099 total)