It was in SQL Server 7 by granting permissions to certain stored procedures. However, that mechanism was unsupported. I've not seen a similar write-up in SQL Server 2000. The problem is too much information goes across that a good developer shouldn't see. Things like who's logged on (Existing Connection), and visibility into other databases that a developer may not on a normal basis have access to see.