About those sp_ sprocs.

I find the replication put many sprocs with sp_ prefix in our database. Do
you think that should be changed? I have been told not to use sp_. See
http://www.sqlmag.com/Article/ArticleID/23011/sql_server_23011.html.
Have never really thought about it, but I suppose the reasoning is that it's
a good way of differentiating these stored procs as system ones. If you are
concerned about the performance issues, then you could raise a connect
case...
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

About those sp_ sprocs

I find the replication put many sprocs with sp_ prefix in our database. Do you think that should be changed? I have been told not to use sp_. See http://www.sqlmag.com/Article/ArticleID/23011/sql_server_23011.html.

Are you asking:

1. if you can change the names of the procs that replication added

or

2. the procs that you are creating, to aviod the prefix sp_?

|||

I was asking 2. Namely when DBA configures replication, can we have an option to choose sproc naming convention, and prefix sp_ should be warned / avoided in database other than master?

But if we can change those names later, that would also be nice to have.

|||

So you want a warning when anyone else tries to create a proc with prefix sp_?

You could probably do something using the database triggers.