sp_helprotect is the system stored procedure used to determine the user level permissions of database objects including tables, stored procedures, user fenide functions, etc.
It displays the users who can access to database object, who granded the permission, type of permission, owner of hte objects, etc.
-- List all user permissions of all Database objects sp_helprotect -- List all user permissions of tblSalary sp_helprotect 'dbo.tblSalary' -- List all user permissions of sp_Get_Salary sp_helprotect 'dbo.sp_Get_Salary' -- List all user permissions of sp_Get_Salary sp_helprotect 'dbo.sp_Get_Salary', 'emp_user' -- List all user permissions of sp_Get_Salary provided by dbo sp_helprotect 'dbo.sp_Get_Salary', null,'dbo' -- List all Object type user permissions sp_helprotect null, null,null,'o' -- List all statement type user permissions sp_helprotect null, null,null,'s'
2007-10-02 (first published: 2002-06-20)
15,404 reads
I have always read that 8060 bytes is the maximum size. This is stated over and over again in Books Online, the MS site and numerous other sites, including this one. However a post in our forum recently questioned this. I decided to verify the problem and do a little research.
2007-10-02 (first published: 2002-02-07)
37,052 reads
The User_Defined_Functions.exe file contains the User-Defined Functions white paper. The User-Defined functions white paper outlines the characteristics of the new user-defined function (UDF) feature that is introduced in Microsoft SQL Server 2000. The white paper also summarizes how you can create your own Transact-SQL functions to extend the programmability of Transact-SQL.
2001-08-31
2,233 reads
The following stored procedure will demonstrate the use of cursor metadata. Using cursor metadata we can get information about an SQL statement and use that information to dynamically generate other code such as HTML or other stored procedures.
2001-07-27
5,064 reads
ne of the issues you face when building Web applications is handling the errors you encounter when interacting with a back-end database. I was recently working with someone to create a new Web site with SQL Server™, ActiveX® Data Objects (ADO), and ASP. Lots of little things came up that I thought were worth sharing with MIND readers, so I'll focus this column on what I learned from this experience and the solutions to many of the problems I faced.
2001-07-13
1,579 reads
