![]() ![]() Rather than having to sift through an entire database to find the data you requested, Crystal Reports lets the server do the sifting and gets back a much smaller set of data, thus reducing the time and resources your workstation must use in order to finish the report. This SQL query is a representation of the SQL statement that Crystal Reports sends to the SQL server.īy interpreting as much as possible from the report design into an SQL query, Crystal Reports can off-load much of the report processing onto the server machine. This query can be seen by choosing Show SQL Query from the Crystal Reports menu. When you design a report that accesses SQL data, Crystal Reports builds an SQL query. When you connect to an SQL database, Crystal Reports acts as an SQL client application, connecting to your SQL server through your network. In the Database Expert, users can select and link tables from a wide variety of data sources, including Microsoft Excel spreadsheets, SQL, Oracle databases, Business Objects Enterprise business views, and local file system informationįor example, if the user wants to display the product details from product table residing in SQL database, then an ODBC connection needs to be established thru Database Expert. Database Expert dialogue box in crystal reports allows the user to select data sources and database fields/ tables in a simple and easier way. ScenarioĬrystal Reports is a business intelligence application used to design and generate reports from a wide range of data sources. ![]() The author has been working on Business Objects projects for the last four years. To use a service name to specify a particular instance, include the service name at the end of the global object name: SELECT * FROM that in this example, there are two symbols.This article describes about Database Expert in Crystal Reports. In this case, just as when a service name is specified as part of the link name, the instance is determined by the USING string. Also notice that in the third example, a service name is not specified as part of the link name. The text of the service name does not necessarily indicate how a connection is to be established this information is specified in the service name of the USING clause. Notice in the first two examples that a service name is simply a part of the database link name. The local database can contain the following public database links to define pathways to the remote instances of the hq database: CREATE PUBLIC DATABASE LINK 'string_to_hq_1' ĬREATE PUBLIC DATABASE LINK 'string_to_hq_2' The hq database has two instances named hq_1 and hq_2. When creating a database link, a service name is specified as the trailing portion of the database link name, separated by an sign, as in This string is called a connection qualifier.įor example, assume that remote database hq. is managed in a Oracle Real Application Clusters environment. To facilitate such functionality, the database lets you create a database link with an optional service name in the database link name. Some clients connect to the Oracle Database server using TCP/IP while others use DECNET. Some cases in which this strategy is useful are:Ī remote database is part of an Oracle Real Application Clusters configuration, so you define several public database links at your local node so that connections can be established to specific instances of the remote database. In some situations, you may want to have several database links of the same type (for example, public) that point to the same remote database, yet establish connections to the remote database using different communication pathways. Using Connection Qualifiers to Specify Service Names Within Link Names Current user links are part of the Oracle Advanced Security option. Note: The current user may not be the same as the connected user, and must be a global user on both databases involved in the link (see "Users of Database Links"). The link uses the userid/password of the current user to log onto the remote database. ![]() The link connects to the remote database with the userid/password of jane/ password regardless of the connected user.ĬREATE DATABASE LINK link_1 CONNECT TO CURRENT_USER USING 'us_supply' Ī private link called link_1 to the database with service name us_supply. So if scott (identified by password) uses the link in a query, the link establishes a connection to the remote database as scott/ password.ĬREATE DATABASE LINK link_2 CONNECT TO jane IDENTIFIED BY password USING 'us_supply' Ī private fixed user link called link_2 to the database with service name us_supply. The link uses the userid/password of the connected user. A private link using the global database name to the remote supply database. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |