This project is read-only.

Manual Database Setup

Note: You normally do not need to run this process unless you really want to manually configure the MSSQL database. By default the application will walk you through the process of setting up the database.

Follow the steps below to manually create the database for uManage and update the application configuration file to use it.
  1. Run the Application Setup Wizard - This creates a lot of the required tie-ins and application settings that you won't have to deal with later like Encryption of the configuration file.
  2. Open SQL Management Studio (uManage works with 2005 and up database engines)
  3. Create a new database (We suggest the following naming format: uManage-<your domain>, an example: uManage-familynet)
  4. Create your login user:
    1. If you want to create your own SQL Authentication user then do that now (Why didn't you use the setup wizard though? It does exactly what your doing now)
    2. If you are using Windows Authentication make sure you have the login added to the database
  5. Install the database:
    1. We include a SQL file (The same one the Wizard uses) to do this
    2. Browse to the application folder
    3. The sql file is located here: AppRoot/App_Data/SQL/uManage-Import.sql
      1. Note: Don't worry about deleting the file later, the App_Data folder is protected from any HTTP requests by IIS
    4. Verify tables, Stored Procedures were created
    5. You must now Execute a Stored Procedure to add a user account in uManage to the admin groups.
      1. For simplicity we have provided a file attachment to these instructions that contains a simple version of the sproc, simply update the username to grant rights to and point it at your database, then execute it.
      2. Download here: AddUserToRoles.sql
  6. After the database is ready the last step is to modify the web.config file in the AppRoot folder:
    1. The only change required will be to the Connection String for AppService.
    2. Because the connection string can really be many things you can research them here:
    3. The only setting we would suggest is to add this to your connection string: "MultipleActiveResultSets=true;"
  7. When the setup wizard is run without a database it takes the application offline so users do not attempt to connect and receive error messages. From the AppRoot folder remove the file: "AppOffline.htm"
  8. The application should now be online

Last edited Aug 9, 2012 at 4:08 PM by rikishipabst, version 2


No comments yet.