How do you configure a new NPM install to use a remote SQL 2005/2008 Standard server without giving the account dbcreator or securityadmin rights? In an environment where a DBA manages the SQL server it can be difficult to get this level.
Thanks,
You are right, you could use the SA or other higher rights, run through the Configuration Wizard. Once it completes, rerun the Configuration wizard and use the Other rights.
Please Note: you will have to do this for every upgrade and Service Pack. Also, if you have an issue support has to deal with and you are not around to note that the User does not have rights, it may delay the amount of time to resolve any potential issue.
Your SQL DBA can create a new SQL Account and have it set the Permissions.
Orion needs it's user account to have DBO rights to the Orion Database. Once the Account has been setup, you can enter in the Remote SQL information in the Configuration Wizard and enter in the Credential Information.
If the Configuration Wizard Fails on the Database, then Orion does not have sufficient Rights to create and Modify the Database.
I had our DBA create a SQL login and a new db called Orion; the SQL login was given DBO rights to this new db but the configuration wizard failed with an error:
Database configuration failed: • Error while executing script- Cannot find the object "dbo.Syslog" because it does not exist or you do not have permissions.
It looks like the SQL login used for setup has to be a dbcreator and securityadmin. I was hoping the config would let us use an existing blank db.
isnt it possible for your dbadmin to give temporary full rights?
Thats what we did... we gave the account full rights to create a db and after that limited it to dbowner and full access to only the orion databases (NPM+NCM)
