Share via

Data Hosting Resource Manager::AllocateDatabase

  • Article

This procedure allocates a database from the resource pool. The allocation is first checked against the organization's quota and then a server is selected from the pool.

Arguments

Argument Required Description

<org>

Yes

The Lightweight Directory Access Protocol (LDAP) path of the owning organization.

<megabytes>

Yes

The size in megabytes that the database can grow to.

<databaseName>

Yes

The name of the Database to allocate.

<serverClassName>

Yes

The server class group to select the server candidate from.

<algorithm>

Yes

Defines the server candidate selection behavior. The allowed values are (note these are case sensitive):

  • tightPack: From the set of servers that can satisfy the capacity of an allocation, the servers are ranked favoring those with the least amount of free space.

  • level: From the set of servers that can satisfy the capacity of an allocation, the servers are ranked favoring those with the most amount of free space.

  • minSeverCount: From the set of servers that can satisfy the capacity of an allocation, servers are selected where the organization has already had databases allocated. If no appropriate servers are found meeting this criteria, then the procedure falls back to a "tightPack" algorithm or the algorithm specified in the @alternate optional parameter.

<algorithm>/@alternate

Yes

Defines the alternate algorithm behavior if the minServerCount algorithm fails to find a candidate server. If provided, this alternate will be used to select the server candidate. If not provided the procedure will default to a "tightPack" alternate. This optional attribute is ignored for all algorithm values except "minServerCount."

<preferredDomainController>

Yes

<serverName>

No

The name of the SQL Server. Overrides automatic selection behavior. However the specified server is still evaluated to see if it has been added to Resource Manager, has the necessary resources to satisfy the request, and is a member of the specified server class.

<container>

No

A starting LDAP container to look for the server in. The procedure performs an LDAP search to resolve the <server>/<serverName> to the Active Directory computer object. You can improve the performance of this search by specifying a default container (e.g. LDAP://CN=Computers,DC=fabrikam,DC=Com).

Remarks

Access Level

Private

Provisioning Steps

  1. Remove the organization quota from Resource Manager.

Security

  • Impersonate Caller.

Note

The access level of this procedure is private. It is intended to be called from other namespaces that perform their own security checks.

Sample Code

Example XML Request

<request> 
  <procedure> 
    <execute namespace="Data Hosting Resource Manager" procedure="DeleteOrganizationQuota" impersonate="1"> 
      <executeData> 
        <org>LDAP://OU=alpineskihouse,OU=consolidatedmessenger,OU=Hosting,DC=fabrikam,DC=Com</org> 
        <preferredDomainController>AD01-wh.fabrikam.com</preferredDomainController> 
      </executeData> 
      <after source="executeData" destination="data" mode="merge" /> 
    </execute> 
  </procedure> 
</request>

Applies To

Data Hosting Resource Manager Namespace API for:

  • Hosted Messaging and Collaboration version 4.5

  • Hosted Messaging and Collaboration version 4.0

  • Hosted Messaging and Collaboration version 3.5

  • Hosted Messaging and Collaboration version 3.0

  • Windows-based Hosting version 4.5

  • Windows-based Hosting version 4.0

  • Windows-based Hosting version 3.5

  • Windows-based Hosting for Applications version 1.0

See also

Tasks

Data Hosting Resource Manager::ModifyDatabaseAllocation