Yes, if your end goal is just to install the database and give the user
that's running the installation ownership to it and login rights, then those
three steps would do it (though you're missing the "user enters sa account
credentials, and server/instance name in custom installer dialog"... You of
I think you're right on the money Troy, and I'll try what you're suggesting
and spend some time because that sounds like a very good idea. I'd like to
try and simplify the steps you outline down to what I've mentioned below...
if that sounds plausible to you guys (I'm asking, because I think the
Seems like the workflow is:
1. Connect to Server B (sql server) using an existing sql login (not
windows), that has less than admin level rights (configured where? created
when?).
2. Somehow obtain different credentials from Server B that have
administrative rights on Server B.
3. Connect with new
If the identity running the installation doesn't have sysadmin privileges,
you're not going to be able to grant anything to yourself... Maybe I'm not
understanding the workflow that you're trying to achieve. We can take it
offline if you like.
-Original Message-
From: [EMAIL PROTECTE
4 matches
Mail list logo
