Abstract: Techniques for query execution against relational databases using connection pooling are described. According to some embodiments, a query processing service is disclosed that enables users to execute queries against target relational databases implemented by a relational database service. The service receives query requests originated by a client application at a web service endpoint and identifies a connection to a particular target database. In some examples, the query request is a Hyper Text Transfer Protocol (HTTP) message comprising a query to be executed by a target database instance within the provider network. The service transmits the query for execution at the target database via the connection and obtains a query result based on the execution of the query. The service transforms the query result into a format suitable for the client and transmits a query response to the client.

Abstract: A proxy server acts as an intermediary between a database client and a database server. The proxy server is configured with a set of user-defined rules. When a request is received from the database client, the proxy server may apply rules that modify, route, reject, log, or pass the request to the database server. Individual rules may be based on attributes of the client computer system, database server, or the request itself. In one embodiment, a rule may be used to translate a request from a format provided by the client into a format preferred by a destination database. In one embodiment, a rule may route a particular request to one of a number of databases based on the nature of the request.

Abstract: A database proxy server provides a web service interface such as a representational state transfer (“REST”) interface to a relational database. The proxy server maps a request submitted via the web service interface to a database interface. In some examples, the web service interface is a stateless REST interface that maps particular SQL statements or subroutines to a request submitted via a particular URL. A web client is able to pass parameters with a request using either URL encoding (the GET method) or within the body of the request (the POST method). The proxy server generates one or more database commands that correspond to the request. The database commands are submitted to the relational database, and the relational database performs the database commands to fulfil the request.

Abstract: A proxy server acts as an intermediary between a database client and a database server. The proxy server establishes and maintains a set of logical connections to the database server. The proxy server receives a request from the database client, and generates a set of database commands that, when performed by the database server, are capable of fulfilling the request. The proxy server selects a particular logical connection from the set of logical connections based at least in part on a characteristic of the request, and submits the set of database commands to the database server via the selected particular logical connection. In various examples, the particular logical connection is selected so that various performance, efficiency, and security objectives are achieved.

Abstract: A proxy server receives requests from a client computer system and generates corresponding sets of database commands that are capable of fulfilling the requests when submitted to a database server. The proxy server may repeat processing associated with a particular request more than once under different operational conditions in order to improve future performance. In some examples, the proxy server submits a particular database command sequence to the database server using various operational parameters, and measures the performance of each submission to identify a particular set of operational parameters to be applied to the database server with future submissions. In another example, the proxy server determines a number of alternative command sequences that fulfill a particular request, and measures the performance of each of the alternative command sequences to determine how command sequences are generated for future requests.

Abstract: An activity is selected. Resource requirement user inputs, indicative of resource requirements for the activity, are received, as are priorities identifying which of the resource requirements are more important than others. Resources are automatically identified based on how well they match the resource requirements, as prioritized, and based on availability. The identified resources are automatically assigned to the activity.

Abstract: A pricing component generates a user interface that allows a user to select dimensions that are to be considered in generating pricing information. The dimensions can be set in a precedence hierarchy so the user can identify which dimensions are used, and the order of evaluation of a price according to those dimensions. Once the user wishes to begin setting the pricing according to the selected dimensions, the pricing component generates another user interface display in order to allow the user to begin setting the prices for combinations of specified dimension values.

Abstract: User values and selections are collected and provided to a report server that customizes a generically defined report pursuant to the user values and selections. An ordered set of report parameters is declared in the definition of a report and then this parameter definition is used to drive user prompting and execution of the report. As parameter values are collected in sequence order, a value retrieved or specified by the user for one parameter may be used to generate the set of the allowed values or default value of a parameter later in the sequence. Parameters are dynamically presented to the user. After values for all parameters been retrieved or specified, a report is generated by the report server.

Abstract: Indexing and storage of context of a plurality of interactive points within an interactive document is provided. The context of the interactive points within the document is stored in a server such that it can be located by the server via the index. Furthermore, information may be received at the server identifying context data for an interactive point stored in the server upon a user activating the interactive point within the document. The server may then transmit to a client the context data stored by the server identified by the information received.

Abstract: A graphical user interface and method of use thereof that allows users to interact with an entity relationship model. The user interface includes zones that allow users to navigate among the entities, roles and fields to create queries that are run against the model. Clicking on an entity in the shows the available fields for the entity. Users can drag and drop entities and fields onto a design surface to quickly and easily build queries. Rules are applied when either an entity or a field is dropped onto the design surface based upon the item being dropped (either an entity or a field), the position of the drop and also the properties that are associated with the item. Entities may be grouped and filtered to sort and limit the results of the query. After query is run, the results may be displayed in a separate area to the user.

Abstract: Systems and methods for supporting custom report layouts allow features that may be available to supported report layouts to also be made available to custom layouts. A custom layout definition may first meet a set of report definition criteria so that it is recognizable to report processing software. A design tool is provided that may be used to create such a custom layout definition. The custom layout may then be passed to report processing software. The report processing software can initially process the custom layout, and provide it with any features available in the initial processing stage. The reporting software may provide an interface for custom processing of the custom layout. The interface may be accessible to custom layout builder objects. Custom layout builder objects can be designed to use the report building components provided through the interface to build a custom report layout.

Abstract: A method, system, and apparatus for discovering and connecting to data sources are provided. A system is provided that includes a server computer operative to maintain a centrally managed repository of data connection definitions. A client computer is also provided including an application program capable of consuming data from a data source. When a request is received by the application to connect to a data source, a list of available sources is retrieved from the server computer. If one of the data sources in the list is selected, a data connection file is retrieved and utilized to connect to the data source. If a report is opened by the application that includes a reference to a data source, the repository is utilized to confirm the connection to the data source.

Abstract: User values and selections are collected and provided to a report server that customizes a generically defined report pursuant to the user values and selections. An ordered set of report parameters is declared in the definition of a report and then this parameter definition is used to drive user prompting and execution of the report. As parameter values are collected in sequence order, a value retrieved or specified by the user for one parameter may be used to generate the set of the allowed values or default value of a parameter later in the sequence. Parameters are dynamically presented to the user. After values for all parameters been retrieved or specified, a report is generated by the report server.

Abstract: Data-driven delivery enables reports to be executed and delivered to a list of recipients, determined at runtime. The data-driven delivery is exposed to users as a type of subscription. For data-driven delivery, a list of recipients is retrieved based on a query specified by an administrator, for example. For each recipient, an optional set of fields is also retrieved, giving the administrator the ability to customize the content of the report for each recipient by mapping the fields returned by the query to report parameters or delivery extension settings. The report is delivered to each recipient using a delivery mechanism specified in the results of the query or when the data-driven subscription is created.