October 24, 2018 at 9:46 am
Comments posted to this topic are about the item Prevent accidental DB drop\delete
October 24, 2018 at 11:52 am
Subhash Chandra - Wednesday, October 24, 2018 9:46 AMComments posted to this topic are about the item Prevent accidental DB drop\delete
Looks like Lowell's code here - same format, same comments, etc:
DDL trigger to prevent drop of a particular database
with a couple really little changes - and one changed incorrectly. When you changed sysname, it should be nvarchar(128) not varchar(128).
I'd stick with Lowell's example.
Sue
October 24, 2018 at 4:58 pm
Sue_H - Wednesday, October 24, 2018 11:52 AMSubhash Chandra - Wednesday, October 24, 2018 9:46 AMComments posted to this topic are about the item Prevent accidental DB drop\deleteLooks like Lowell's code here - same format, same comments, etc:
DDL trigger to prevent drop of a particular databasewith a couple really little changes - and one changed incorrectly. When you changed sysname, it should be nvarchar(128) not varchar(128).
I'd stick with Lowell's example.Sue
That and stop posting stuff as if it were your own when it's not. I understand that there's only a certain number of ways to write code but, like Sue said, the comments and even the spacing of the code are identical to Lowell's. There's only one way that can happen.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2018 at 5:15 pm
Jeff Moden - Wednesday, October 24, 2018 4:58 PMSue_H - Wednesday, October 24, 2018 11:52 AMSubhash Chandra - Wednesday, October 24, 2018 9:46 AMComments posted to this topic are about the item Prevent accidental DB drop\deleteLooks like Lowell's code here - same format, same comments, etc:
DDL trigger to prevent drop of a particular databasewith a couple really little changes - and one changed incorrectly. When you changed sysname, it should be nvarchar(128) not varchar(128).
I'd stick with Lowell's example.Sue
That and stop posting stuff as if it were your own when it's not. I understand that there's only a certain number of ways to write code but, like Sue said, the comments and even the spacing of the code are identical to Lowell's. There's only one way that can happen.
is there an option to flag the item itself as being a possible copy from another one? many people will only see the top link and assume it was done by the individual posting it.
October 24, 2018 at 8:17 pm
frederico_fonseca - Wednesday, October 24, 2018 5:15 PMJeff Moden - Wednesday, October 24, 2018 4:58 PMSue_H - Wednesday, October 24, 2018 11:52 AMSubhash Chandra - Wednesday, October 24, 2018 9:46 AMComments posted to this topic are about the item Prevent accidental DB drop\deleteLooks like Lowell's code here - same format, same comments, etc:
DDL trigger to prevent drop of a particular databasewith a couple really little changes - and one changed incorrectly. When you changed sysname, it should be nvarchar(128) not varchar(128).
I'd stick with Lowell's example.Sue
That and stop posting stuff as if it were your own when it's not. I understand that there's only a certain number of ways to write code but, like Sue said, the comments and even the spacing of the code are identical to Lowell's. There's only one way that can happen.
is there an option to flag the item itself as being a possible copy from another one? many people will only see the top link and assume it was done by the individual posting it.
I flagged it as a "Terms of use" violation. Hopefully, someone that's supposed to monitor such flags at SSC/RC will take a look. If not, I'll hum a rock at Steve's window and see what he thinks.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2018 at 8:56 am
Script removed. User warned
October 26, 2018 at 9:19 am
Steve Jones - SSC Editor - Friday, October 26, 2018 8:56 AMScript removed. User warned
Thanks, Steve.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply