Abstract: A unified communication (UC) application integrates support actions with client communications. In response to receiving an escalation of an issue from a support technician, the UC client application initiates a communication between a responder and a target device associated with the issue. The communication is limited based on privileges of an account used to initiate the communication. A user interface component associated with the communication is provided to enable interactions with the target device. The user interface component is selected based on an instant message, an audio, a video, a remote control session, and similar modality used to communicate with the target device and additional responders. Communications associated with the issue are integrated into a communication session. A history of the session is also recorded and formatted into a timeline list. The history is provided in a subsequent issue having common attributes with the issue.

Abstract: Provided are systems and methods that facilitate providing permission to entities of a database. A system includes a component that authorizes a principal of a containing entity to grant a permission to that entity, and a component that grants the permission to the containing entity, the grantee of the permission inherits a set of permissions to one or more entities contained by the containing entity. When a permission is granted to a parent in a hierarchy of a relational database, the permission is inherited by the child nodes. Also provided is a method for transferring ownership of entities in a relational database. The method includes a two-part handshake that can be audited to avoid repudiation issues.

Abstract: A system and method are presented for providing system code to a variety of databases by using a resource database. The resource database contains pre-created system objects, which have been parsed and organized into a format suitable for execution. These pre-created system objects are capable of logically appearing in the variety of databases, while physically persisting in the resource database. Employing the resource database allows for quick upgrades and rollbacks since the pre-created system objects can be copied and installed on computer systems in a single file-copy operation. Additionally, the resource database limits accessibility to its pre-created system objects, thereby ensuring the integrity of the resource database. Lastly, the resource database contains its own metadata that is distinct from the metadata of the variety of databases.

Abstract: Translation architecture that facilitates translation between schema data and relational structures. The architecture includes a translation component that consumes schema data (e.g., an XML schema) that includes a schema structure, validates the schema structure, and persists in memory a representation of the schema as a relational format. Since schemas are shredded into tables, instance validation loads only the necessary components to perform validation. During validation, only parts of the schema that are used are loaded and cached. A schema cache stores the in-memory representation of schema optimized for instance validation.