Hello again to all,

I posted this question in the Oracle group first and got no responses, so I'm hoping I get better luck here.

The reason I posted this there first is because I know the concept in Oracle and was hoping that someone who knew Oracle and SQL Server would understand the analog concept in SQL Server. But again, no luck.

In Oracle, there is a database object called a SYNONYM. In a nutshell, a synonym is like an alias you can give an object which you can make public or private that allows users to refer to the object as long as they have underlying privledges on the base object. This allows users to call or proc or select from a table using the synonym and avoids them having to always type out <database>.<owner>. before the object name. It is handy. It can also keep your users from knowing the owner (schema name) of the base object for security reasons -- but that's not my main goal here.

I have two stored procs that I want to make available to all our SQL Server developers and have noticed that for system stored procs, one can just call them by typing sp_sysprocname. Is there anyway to give my procs the same functionality so that other developers won't have to type <database>.<owner>.<sp_myprocname> <parameter> and can just run the proc by typing sp_myprocname <parameter> ?

Thanks for any assistance.

If you do not have a constraint of where (on which database) to create the stored procedures, I think you achieve this by creating the stored procedures in Master database with the name staring with "sp_" and with "dbo" previleges.

SQL Server looks in Master database first and executes if the stored procedure name is starting with "sp_".

Thanks ram2098, I will try that.