March 28, 2006 at 12:37 pm
Our developers want to move the sql 2000 tables and SP's from a development database into an existing production database. Furthermore, they would like to have a new production account that can only access the newly moved tables/SP’s but nothing else in the larger database. They also suspect there may be many more development tables\sp’s in the future and moved into the same database. All this is doable but seems a painful way to proceed. How would you approach this problem?
TIA,
Bill
(**** I though I posted this question to this newsgroup hours ago but it hasn't shown up. If it is a re-post, I apologize.)
March 28, 2006 at 12:49 pm
We have a couple of databases like this. Different sets of tables in the database are used by different groups of employees in the same division.
We have an application user (SQL Server login) for each group and each application user has EXEC permission only for the stored procedures that access a particular set of tables.
We've chosen to name the tables and stored procedures for each work group with a unique word e.g. RATIO for one group, CAPS for another group, etc.
We haven't had any major problems with this. There are a lot of tables and stored procedures in the database, but the naming convention groups them together when viewed in Enterprise Manager.
Greg
Greg
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply