Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2006-04-06 : 20:06:02
|
| Tom writes "Hi allI have a unusual situation. We have an application that was developed in two phases. The first phase utilized ADO (from MS C++ .NET2003). The second phase utilized ADO and also added DMO. The need for DMO came about when we needed to copy/backup/restore db's via our application. I know it is probably unusual to do this but oh well.Here's the setup: (most of which is customer requirements)Windows 2003 serverSQL 2K SP3Client PCs running our application.The app manages a 'master' database. The user has the ability to create a subset of the items in the master database. Again, customer driven. The only way we could do this easily and within a budget was to simply copy the master db and then remove the items they didn't select. There are many tables that make up the db so it wasn't clean enough to simply create a new db from scratch and then copy just the data they wanted AND keep all the PK/SK integrity in place.We are using Windows Authentication to allow user access to the databases. However, in order to use DMO we had to create a user account in SQL that had the permissions (basically an sa like account) to create databases, copy databases, backup/restore databases, etc.My question is, how would I setup security (users/roles) that will propagate with the db's as they are created?ThanksTom" |
|
|
|
|
|
ADO/DMO mixed usage