SQL Server 2000General discussion of Microsoft SQL Server -- for topics that don't fit in one of the more specific SQL Server forums. version 2000 only. There's a new forum for SQL Server 2005.
Welcome to the p2p.wrox.com Forums.
You are currently viewing the SQL Server 2000 section of the Wrox p2p Programmer to Programmer discussion community. This is a community of more than 40,000 computer programmers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining our free Wrox p2p community you can post your own programming questions and respond to other programmers’ questions. Registered users also don't have to see the ads that are displayed to guests. Registration is fast, simple and absolutely free so please, join today!
Join today and post to win prizes! Post more to increase your chances of being Wrox’s top poster of the month.
I knew that the questions which i asked in subject must be interesting if we find any solution.
We have already developed an ERP with Visual Basic 6.0 as front-end and SQL Server 2000 as back-end. We have introduce an application role which is used for data access through application. But we dont want sysadmin role users to view / alter the database using SQL Server Enterprise Manager or query analyzer. So is it possible to block sysadmin role users?
Same results have already achieved in SAP B1 in which we can't access stored procedures in the database. As it is possible in SAP
can we implement same functionality in our application
Blocking sysadmin role users...is it possible?
Linear Mode
