Abstract: Various technologies and techniques are disclosed for searching for and extracting data from databases of content management applications. User input is received to connect to a database or database snapshot of an application, and a connection is established. When the database is not part of a current live instance of the application, an emulation is performed such that the database is treated like it is attached to the current live instance of the application. The user is able to browse and/or search for content, including documents, in the database or database snapshot without having to explore individual site collection structure and user interfaces of individual sites. A site collection user interface (UI), a site selector UI, and/or a list selector UI, for example, provide data entry fields for entering search requirements. Unattached databases can be managed using commands, such as using an object model or command line.

Abstract: Technologies are described herein for managing database snapshots. One user interface is provided for managing the automated creation and deletion of database snapshots. Parameters are received through the user interface that define how the database snapshots should be created and deleted. Once the parameters are defined, a timer job is executed that causes a DBMS to create and delete the database snapshots according to the specified parameters. A user interface is also provided for manually managing the creation, deletion, and restoration of database snapshots. A request may be received through this user interface to recover data from a database snapshot. In response to such a request, another user interface is provided for specifying the data that should be recovered. Once the data to be recovered has been specified, the desired data is recovered from the database snapshot.

Abstract: Various technologies and techniques are disclosed for searching for and extracting data from databases of content management applications. User input is received to connect to a database or database snapshot of an application, and a connection is established. When the database is not part of a current live instance of the application, an emulation is performed such that the database is treated like it is attached to the current live instance of the application. The user is able to browse and/or search for content, including documents, in the database or database snapshot without having to explore individual site collection structure and user interfaces of individual sites. A site collection user interface (UI), a site selector UI, and/or a list selector UI, for example, provide data entry fields for entering search requirements. Unattached databases can be managed using commands, such as using an object model or command line.

Abstract: Various technologies and techniques are disclosed for restricting security levels that can be used with browser-based applications. When a request is received from an external application to retrieve data for use in a client browser, an intersection is performed on a permission set of a user of the client browser and of the external application to determine a new permission set to use for retrieving the requested data. Techniques for restricting operations of an external application that is being run in a client browser are also described. A session token is returned to a client browser after validating access can be granted to the client browser. Validation is performed to confirm access can be granted to an external application. A request for data is received from the external application, with the request for data containing the session token. The requested data is retrieved and returned to the external application.

Abstract: Technologies are described herein for managing database snapshots. One user interface is provided for managing the automated creation and deletion of database snapshots. Parameters are received through the user interface that define how the database snapshots should be created and deleted. Once the parameters are defined, a timer job is executed that causes a DBMS to create and delete the database snapshots according to the specified parameters. A user interface is also provided for manually managing the creation, deletion, and restoration of database snapshots. A request may be received through this user interface to recover data from a database snapshot. In response to such a request, another user interface is provided for specifying the data that should be recovered. Once the data to be recovered has been specified, the desired data is recovered from the database snapshot.