Viewing 8 posts - 1 through 8 (of 8 total)
January 27, 2008 at 8:07 pm
Sent you a pm to the site containing the script.
January 25, 2008 at 10:37 pm
There's a lockdown script, for SQL Server 2000, over at SQLSecurity that has code to reduce the exposer to xp_cmdshell without deleting it or any other system stored procedures.
January 25, 2008 at 8:04 am
"Some stored procs contain sensitive logins and passwords"
You might want to think about encrypting these stored procs.
As an alternative you might want to think about storing the id & encrypted...
April 27, 2005 at 10:04 pm
Once you have all null values updated to 7.45 in the table, you may want to set Col014 to not null and set a default value of 7.45 on the...
March 9, 2005 at 7:43 pm
Thanks.
Will look into how many rows have shared locks.
Will it retain the Shared lock obtained during the select until the commit after the DB2 transaction? If this is the...
November 4, 2004 at 11:48 pm
As I understand it, you want to perform the following for records where field na = parameter @na_1.
1. If the current value of the field is 0 or Null, set...
August 23, 2004 at 9:57 pm
If the VB app only uses stored procs and/or views (a good practice for both security and performance), you can grant execute permission on the SPs or select on the...
August 23, 2004 at 8:18 pm
Viewing 8 posts - 1 through 8 (of 8 total)