Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Installation Wizard - Database Permissions

I recently upgraded my Orion from 8.0 to 8.1 and ran into a little snag - SQL Server Permissions.

SQL Server Permission Problem:
The installation was connecting to an existing database on a SQL Server that is hosting many databases for various systems. The database already esisted: SW_ORION. The Orion setup wizard really only needed to modify was the existing database. The wizard would not complete unless the service account was a local admin on the box or had SA level permissions.

According to SW technical support, granting the setup SA rights was the only way that would ensure that the setup could complete properly. I have seen this from many other vendors who sell products that connect to SQL in the back-end. The Wizard could have very easily connected to the server and I could have selected the existing database for the installation. Having DBO (Database Owner) level of permissions would have been plenty to upgrade the tables, stored procedures, etc...

I find it really mind boggling that a company like Solarwinds can sell a product on it's 8th revision that hasn't figured out that giving SA level rights to the database server is not the proper method for installing a SQL Database. Setting up a database on the SQL server and restricting access to Solarwinds Installation wizard just make good security sense.

Anyone else run into this problem?

Find more posts tagged with

Accepted answers

All comments

FormerMember

We realize that the current requirement is not ideal. We plan to improve this in the next release of Orion so that "sa" will not be needed during setup.

thx1138

This is the way Orion works to my knowledge. During the Orion install, you are prompted for a SA account (used to create the DB and tables, etc), THEN you are prompted for a DB access account (used for the application to access the DB), that can manage only that DB, no the entire server.

Have your DBA lock it down after that-

daxvancamp1

I run in to same problem EVERYTIME I do an upgrade/installation and find it annoying !

Please make a hotfix for this because I'm having a problem with an installtion now.

FormerMember

In 8.5, you should be able to avoid use of the sa account if you have a DBA create a database for you beforehand.