Putting sp_ at the beginning of your stored procedure.

, 2014-11-24

Every now and again you see articles and posts about putting sp_ at the beginning of a stored procedure. So what does that do and why should we care? The primary effect is that if you put a stored procedure starting with sp_ in master you can call it directly from any database.

USE master;
GO
CREATE PROCEDURE sp_Test AS
PRINT 'This SP is run from the master DB';
GO
USE Test;
GO
EXEC sp_Test;
GO
This SP is run from the master DB

Well that is fairly useful. Of course you could have easily called it using master.dbo.sp_Test too. So what happens if we already have an sp_Test stored procedure in the original database?

USE Test;
GO
CREATE PROCEDURE sp_Test AS
PRINT 'This SP is run from the Test DB';
GO
EXEC sp_Test;
GO
This SP is run from the Test DB

Simple enough. It will call the version of the SP from the current database rather than the version in master.

Now here is another interesting test with maybe a bit less obvious result.

USE Test;
GO
DROP PROCEDURE sp_Test;
GO
USE master;
GO
ALTER PROCEDURE sp_Test AS
SELECT DB_NAME();
SELECT * FROM sys.sysfiles;
GO
USE Test;
GO
EXEC sp_Test;
GO

SPStoredProcedure

Isn’t that interesting? The GUI shows our current context as Test, DB_NAME shows our current context as Test but when querying a database specific system view it’s clearly looking at the version out of master. So what does that mean for us? If you plan on creating an SP like this that needs to use system views you will need to take this into account. One of the easiest ways to handle this is going to be dynamic SQL, by either generating code with a USE before the beginning of the query or by generating a three part name for each of the system tables/views you plan on querying.

Filed under: Microsoft SQL Server, SQLServerPedia Syndication, System Databases, System Functions and Stored Procedures, T-SQL Tagged: code language, language sql, microsoft sql server, system databases, system functions, T-SQL

Rate

Share

Share

Rate

Related content

Database Mirroring FAQ: Can a 2008 SQL instance be used as the witness for a 2005 database mirroring setup?

Question: Can a 2008 SQL instance be used as the witness for a 2005 database mirroring setup? This question was sent to me via email. My reply follows. Can a 2008 SQL instance be used as the witness for a 2005 database mirroring setup? Databases to be mirrored are currently running on 2005 SQL instances but will be upgraded to 2008 SQL in the near future.

2009-02-23

1,567 reads

Networking - Part 4

You may want to read Part 1 , Part 2 , and Part 3 before continuing. This time around I'd like to talk about social networking. We'll start with social networking. Facebook, MySpace, and Twitter are all good examples of using technology to let...

2009-02-17

1,530 reads

Speaking at Community Events - More Thoughts

Last week I posted Speaking at Community Events - Time to Raise the Bar?, a first cut at talking about to what degree we should require experience for speakers at events like SQLSaturday as well as when it might be appropriate to add additional focus/limitations on the presentations that are accepted. I've got a few more thoughts on the topic this week, and I look forward to your comments.

2009-02-13

360 reads