Adding an Administrator to a Database

This help file applies to an out-of-date version of MainBoss.
The most recent version of MainBoss is MainBoss 4.2.3.
This help file does not exist in MainBoss 4.2.3, but the index for that version can be found here.

< Previous section  |  Table of Contents  |  Index  |  Next section >

The BreakIn verb of MBUtility gives you a way to plant your own login name in the Users table of an existing database, and to give yourself MainBoss Administration privileges. To use this function, you need SQL Server Administrator privileges.

For information on user records, see the reference manual or the online help.

The format of the BreakIn command is:

mbutility BreakIn option option ...

where the options are:

The name of the maintenance organization (associated with your MainBoss database). This name is case-insensitive; for example, MainBoss is the same as mainboss.
The name of the server that holds the MainBoss database.
The name of the MainBoss database.

If you specify /OrganizationName, you don't have to specify either /DataBaseServer or /DataBaseName. If you don't specify /OrganizationName, you must specify both of /DataBaseServer and /DataBaseName.

Specifies a Contacts table entry to be associated with the created User record. For example,
/cc:"Joe Smith"
indicates that the User record should be associated with the Contacts record with the name Joe Smith. If your login name is already in the Users table, you should not specify this command line argument; otherwise, the argument is mandatory.

When the user record is created, it will be in your name (i.e. the login name of whoever executes the MBUtility BreakIn). If your domain is the same as the domain of the SQL Server that manages the MainBoss database, the user record will specify your login name and a blank scope. If your domain is different from the SQL Server's, then "Scope" will specify your domain name. The created user record will give you the MainBoss Administration security role, which allows you to give yourself additional security roles if necessary.

< Previous section  |  Table of Contents  |  Index  |  Next section >