What's the difference between Logic Studio 8 & 9?

is it me or is the ONLY difference between Logic Studio 8 & 9 the fact the LS9 can run in 64-bit mode?
I've owned Logic Studio 8 since about a year after it came out. About a year ago I got a Pro that's got Snow Leopard on it, so I installed LS8 on it. My Pro is running in 64-bit mode, but LS8 only runs in 32-bit mode, so I thought I'd "Upgrade" & buy Logic Studio 9 a couple of days ago. I just installed it yesterday & ran it for the first time today. I don't see ANY differce at all between 8 & 9 EXCEPT that Logic Pro & Main Stage both have a 64-bit mode. ALL of the synths & their presets are the same. All of the loops & jam packs look the same. Did I just pay all that $$$ just to get a 64-bit version of what I already had?
I've tried looking on this site & everything I find is about Logic Pro X. Is there anyone out there that knows enough about this to tell me for sure what the real differences are between Logic Studio 8 & 9?

Check Wikipedia - of course there are more differences:
Logic Pro 9
On July 23, 2009, Logic Pro 9 was announced. A major new feature included "Flex Time", Apple's take on "elastic" audio, which allows audio to be quantized.[5] A version of the pedalboard from GarageBand was included, together with a new virtual guitar amplifier where the modeled components could be combined in different ways. There were also a number of improvements to audio editing, fulfilled user requests such as "bounce in place" and selective track and channel strip import, as well as an expanded content library including one more Jam Pack. Some of the bundled software, including MainStage 2 and Soundtrack Pro 3, was also improved. Logic Pro 9 is Universal Binary, although not officially supported for use on PowerPC computers.[6] SoundDiver, which had been quietly bundled with previous versions, was dropped, eliminating support for arguably the world's most popular synthesizer editor/librarian. As Apple has bundled so many software instruments with Logic, it is not likely that we'll see the return of integration with external synthesizer hardware to the Logic platform.[citation needed]
On January 12, 2010, Apple released Logic Pro 9.1, an Intel only release, thereby officially discontinuing Logic for the PowerPC platform. Logic Pro 9.1 has the option of running in 64 bit mode, which allows the application to address more memory than in the past. Says Apple "With 64-bit mode, the application memory is not limited to 4GB as with 32-bit applications, so there is essentially no practical limit by today's standards.". Third party plug-ins that are 32 bit are still compatible, but will run from a 'wrapper' inside Logic Pro itself.
On December 9, 2011, Apple announced that Logic Pro Studio 9 would no longer be available on DVD, and would only be sold via the Mac App Store. The price was reduced from $499 to $199.99 for the Logic Pro app, and $29.99 for MainStage. The download was just over 400mb, and 19gb of optional loops were available as in-app downloads.[7]

Similar Messages

What is the difference between logic studio academic version and the normal version ?

what is the difference between logic studio academic version from the other versions ?

No difference... the Academic version cannot be upgraded to the next major revision.
If you had putchased the Logic 9 academic version you get all the updates 9.0, 9.03, 9.1, 9.3...etc
When Logic 10 rolls around you would have to purchase the application at full price, your version isn't elgible for the upgrade price.
Same software as the retail version though.
pancenter-

What is the difference between logical ROWID and physical ROWID

hello
can u please explain the difference between logical ROWID and physical ROWID
regards,

from the docs (a 30 sec search)
Physical rowids store the addresses of rows in ordinary tables (excluding index-organized tables), clustered tables, table partitions and subpartitions, indexes, and index partitions and subpartitions.
Logical rowids store the addresses of rows in index-organized tables.

What's the Difference Between Logic Board Failure and Hard Drive Failure

Hi!
So I wanted to know the difference between a Logic Board Failure and Hard Drive Failure because a couple of days ago I tried starting my computer up and I was welcomed by the Apple chime and a grey screen. I have been researching and most people say its either the hard drive or the logic board. So I am curious to know what are the symptoms of both. Thanks a lot, in advance!

The hard drive is where the OS resides, if it dies there is no OS loading, so you can't boot. If you hook up your external drive with your clone of the internal drive, boot up and hold down the option key, select your clone drive as the startup drive in boot manager that then appears, and the computer boots normally, then the computer is OK, it is just the internal drive that has gone south. You don't have a clone to boot from? Now you know why you should.
You could try booting from the DVD that came with the computer, hold down the "D" key to run diagnostics and see what the results are. If you can't boot into the diagnostics then a trip to the Apple store is probably in order.
Francine
Francine
Schwieder

What is the difference between Logical Disk and Physical Disk?

Hi.
When I do Performance Monitor, I got Logical Disk Avg. Disk sec/Write counter and Physical Disk Avg. Disk sec/Write counter.
But I can see the different Avg. value and Max. value.
Even if Logical and Physical Disk are one-to-one mapping.
Why did i get the result?
One the other hands, I got a same result that Logical Disk Avg. Disk sec/Read counter and Physical Disk Avg. Disk sec/Read counter's Avg. value and Max. value.

Physical Disk refers to an actual physical HDD (or array in a hardware RAID setup), whereas Logical Disk refers to a Volume that has been created on that disk.
So if you have one disk with one volume created on it then the values are likely to be 1 to 1, but if you have multiple volumes on the disk, for instance a physical disk with C:\ and D:\ volumes running on it, then the logical disks relate to c:\ and d:\
rather than the disk they're running on.
See
http://blogs.technet.com/b/askcore/archive/2012/03/16/windows-performance-monitor-disk-counters-explained.aspx for a more in depth explanation.

Difference between logic studio n logic express 9, difference between logic studio n logic express 9

What's the diff between logic studio and lodic express 9? If i were to get either 1 of it, which Mac Pro shld i get? 13" or 15"

Hi,
Logic Studio: Logic Pro 8, Soundtrack Pro and MainStage.
So yes, Logic Pro 8 is part of the 'Logic Studio' package, which also contains the two other apps.
http://www.apple.com/logicstudio/
Take a look at the Logic Pro 8/Logic Studio forum. There are mixed opinions on whether it is worth upgrading yet or not.
Good Luck!
Steve

What is the difference between != and Logical NOT operator

kindly,tell me what is the difference between Not Equality operator and logical negation operator.
Edited by: user13414134 on Dec 3, 2010 8:59 AM

what is the difference between != and Logical NOT operator The NOT operator is transformed into the inequality operator (<>), as can be seen from the Predicate Information of the explain plan:
SQL> explain plan for select * from dual where :x != :y
Explain complete.
SQL> select * from table(dbms_xplan.display())
PLAN_TABLE_OUTPUT
Plan hash value: 3752461848
| Id | Operation          | Name | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT   |      |     1 |     2 |     2   (0)| 00:00:01 |
|* 1 | FILTER            |      |       |       |            |          |
|   2 |   TABLE ACCESS FULL| DUAL |     1 |     2 |     2   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   1 - filter(:Y<>:X)
14 rows selected.
SQL> explain plan for select * from dual where not :x = :y
Explain complete.
SQL> select * from table(dbms_xplan.display())
PLAN_TABLE_OUTPUT
Plan hash value: 3752461848
| Id | Operation          | Name | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT   |      |     1 |     2 |     2   (0)| 00:00:01 |
|* 1 | FILTER            |      |       |       |            |          |
|   2 |   TABLE ACCESS FULL| DUAL |     1 |     2 |     2   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   1 - filter(:Y<>:X)
14 rows selected.

What is the difference between HTML DB and HTML DB Studio?

What is the difference between HTML DB and HTML DB Studio?

Doug,
Oracle HTML DB is a feature of the Oracle 10g Database which allows you to quickly & securely create web applications based on your data in Oracle.
Please see our homepage on OTN for more details: http://otn.oracle.com/htmldb
Oracle HTML DB Studio is a site where you can download HTML DB applications, utilities & tip and tricks for use with HTML DB.
Thanks,
- Scott -

What's the Difference Between OLAP and OLTP?

HI,
What's the difference between OLAP and OLTP ? and which one is Best?
-Arun.M.D

Hi,
The big difference when designing for OLAP versus OLTP is rooted in the basics of how the tables are going to be used. I'll discuss OLTP versus OLAP in context to the design of dimensional data warehouses. However, keep in mind there are more architectural components that make up a mature, best practices data warehouse than just the dimensional data warehouse.
Corporate Information Factory, 2nd Edition by W. H. Inmon, Claudia Imhoff, Ryan Sousa
Building the Data Warehouse, 2nd Edition by W. H. Inmon
With OLTP, the tables are designed to facilitate fast inserting, updating and deleting rows of information with each logical unit of work. The database design is highly normalized. Usually and at least to 3NF. Each logical unit of work in an online application will have a relatively small scope with regard to the number of tables that are referenced and/or updated. Also the online application itself handles the majority of the work for joining data to facilitate the screen functions. This means the user doesn't have to worry about traversing across large data relationship paths. A heavy dose of lookup/reference tables and much focus on referential integrity between foreign keys. The physical design of the database needs to take into considerations the need for inserting rows when deciding on physical space settings. A good book for getting a solid base understanding of modeling for OLTP is The Data Modeling Handbook: A Best-Practice Approach to Building Quality Data Models by Michael C. Reingruber, William W. Gregory.
Example: Let's say we have a purchase oder management system. We need to be able to take orders for our customers, and we need to be able to sell many items on each order. We need to capture the store that sold the item, the customer that bought the item (and where we need to ship things and where to bill) and we need to make sure that we pull from the valid store_items to get the correct item number, description and price. Our OLTP data model will contain a CUSTOMER_MASTER, A CUSTOMER_ADDRESS_MASTER, A STORE_MASTER, AN ITEM_MASTER, AN ITEM_PRICE_MASTER, A PURCHASE_ORDER_MASTER AND A PURCHASE_ORDER_LINE_ITEM table. Then we might have a series of M:M relationships for example. An ITEM might have a different price for specific time periods for specific stores.
With OLAP, the tables are designed to facilitate easy access to information. Today's OLAP tools make the job of developing a query very easy. However, you still want to minimize the extensiveness of the relational model in an OLAP application. Users don't have the wills and means to learn how to work through a complex maze of table relationships. So you'll design your tables with a high degree of denormalization. The most prevalent design scheme for OLAP is the Star-Schema, popularized by Ralph Kimball. The star schema has a FACT table that contains the elements of data that are used arithmatically (counting, summing, averaging, etc.) The FACT Table is surrounded by lookup tables called Dimensions. Each Dimension table provides a reference to those things that you want to analyze by. A good book to understand how to design OLAP solutions is The Data Warehouse Toolkit: Practical Techniques for Building Dimensional Data Warehouses by Ralph Kimball.
Example: let's say we want to see some key measures about purchases. We want to know how many items and the sales amount that are purchased by what kind of customer across which stores. The FACT table will contain a column for Qty-purchased and Purchase Amount. The DIMENSION tables will include the ITEM_DESC (contains the item_id & Description), the CUSTOMER_TYPE, the STORE (Store_id & store name), and TIME (contains calendar information such as the date, the month_end_date, quarter_end_date, day_of_week, etc).
Database Fundamentals > Data Warehousing and Business Intelligence with Mike Lampa
Search Advice from more than 250 TechTarget Experts
Your question may have already been answered! Browse or search more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.

What's the difference between shuffle and shuffle all?

What's the difference between shuffle and shuffle all?

Thanks but I have no playlists. Perhaps you know then how the buttons work:
ie. when "shuffle" is showing, does that mean it set to "shuffle all" and vice versa?
the logic on these Iphones is whacky...
Thanks!

What is the difference between ALE & EDI

What is the difference between ALE & EDI ? [in case of its configuration.]

hi,
chk out this
ALE Configuration     1
1     ALE Introduction Transaction SALE
2     The 3 ALE methods
2.1     Push
2.1.1     First create logical system (In SPRO / SALE)
2.1.2     Assign Client to Logical System (In SPRO)
2.1.3     Create RFC Destination SM59
2.1.4     Create Distribution Model BD64
2.1.5     Send Material BD10     9
2.1.6     Check IDOC sent WE02
2.2     Pull
2.2.1     Create Model View BD64
2.2.2     Login to 810
2.2.3     Get Material BD11
2.2.4     Check IDOCs WE02
2.2.5     Check Material MM02
2.3     Change Pointer
2.3.1     Activate change pointers for message type BD50
2.3.2     Activate Change Pointers BD61
2.3.3     Execute RBDMIdoc SE38
2.3.4     Check IDOCs WE02
2.3.5     Check Material MM02
EDI configuration
1) have to configure EDI subsytem
2) Configure basic edi components
3) Configure Partner Profiles
4)    "             Message Control
       The main difference is that you have to configure the subsytem in case of EDI where as this is not the case of ALE.
     EDI uses memory buffer while ALE uses file port.
<b>Reward useful points</b>
ALE/EDI
Regards
SIva

What is the difference between ABAP and HR-ABAP?

Hi people,
Could u just tel me abt what is the difference between ABAP and HR-ABAP?
Thanks in advance,
Sanjeev K.V

Hi Sir ,
Please have a look below .Hope it is suitable and simpler solution for your question.
Please do reward if useful.
Thankx.
HR deals with the INFOTYPES which are similar to Tables in General ABAP.
There are different ways of fetching data from these infotypes.
There are different areas in HR LIKE Personal Admn, Orgn Management, Benefits, Time amangement, Event Management, Payroll etc
Infotypes for these areas are different from one another area.
storing of records data in each type of area is different
LDBS like PNP are used in HR programing.
Instead of Select.. we use some ROUTINES and PROVIDE..ENDPROVIDE.. etc
and in the case of Pay roll we use Clusters and we Import and Export them for data fetching.
On the whole Normal ABAP is different from HR abap.
Also,
HR:
HR deals with the INFOTYPES which are similar to Tables in General ABAP.
There are different ways of fetching data from these infotypes.
There are different areas in HR LIKE Personal Admn, Orgn Management, Benefits, Time amangement, Event Management, Payroll etc
Infotypes for these areas are different from one another area.
storing of records data in each type of area is different
LDBS like PNP are used in HR programing.
Instead of Select.. we use some ROUTINES and PROVIDE..ENDPROVIDE.. etc
and in the case of Pay roll we use Clusters and we Import and Export them for data fetching.
On the whole Normal ABAP is different from HR abap.
For Personal Admn the Infotypes start with PA0000 to PA1999
Time Related Infotypes start with PA2000 to PA2999.
Orgn related Infotypes start with HRP1000 to HRP1999.
All custom developed infotypes stsrat with PA9000 onwards.
In payroll processing we use Clusters like PCL1,2,3 and 4.
Instead of Select query we use PROVIDE and ENDPROVIDE..
You have to assign a Logical Database in the attributes PNP.
Go through the SAp doc for HR programming and start doing.
http://www.sapdevelopment.co.uk/hr/hrhome.htm
See:
http://help.sap.com/saphelp_46c/helpdata/en/4f/d5268a575e11d189270000e8322f96/content.htm
sites regarding hr-abap:
http://www.sapdevelopment.co.uk/hr/hrhome.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PAPA/PAPA.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PAPD/PAPD.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PYINT/PYINT_BASICS.pdf
http://www.atomhr.com/training/Technical_Topics_in_HR.htm
http://www.planetsap.com/hr_abap_main_page.htm
You can see some Standard Program examples in this one ...
http://www.sapdevelopment.co.uk/programs/programshr.htm
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci1030179,00.html?Offer=SAlgwn12604#Certification
http://www.erpgenie.com/faq/hr.htm.
http://www.planetsap.com/hr_abap_main_page.htm
http://www.sapbrain.com/TUTORIALS/FUNCTIONAL/HR_tutorial.html
These are the FAQ's that might helps you as well.
http://www.sap-img.com/human/hr-faq.htm
http://www.sapgenie.com/faq/hr.htm
http://www.planetsap.com/hr_abap_main_page.htm
http://www.atomhr.com/library_full.htm
HR Long texts Upload
Look at the below link
And finally,
Few notes are below:
InfoSets in the HR Application
You can use SAP Query in HR to report on HR data. Queries are maintained as described in Creating Queries. The special features of queries created for HR are described in Maintaining Queries in the Human Resources Application. The maintenance procedure for HR InfoSets differs from the described procedure inasmuch as HR data fields are grouped together in infotypes.
InfoSet management in SAP Query is also used for InfoSet Query. For further information, see Functions for Managing InfoSets.
If you want to create InfoSets for HR, you can use logical databases PNP, PNPCE, PAP, and PCH (see HR Logical Databases). The database you must use to create your InfoSet depends on the component in which the data you want to report on is stored.
The reports you can execute using InfoSets based on logical databases PNP (or PNPCE) or PCH are similar, but differ in that they can select different objects. The following table describes the connection between the logical database, and the infotypes you can include in an InfoSet. It also provides you with one or two examples of reports that you can execute using the appropriate InfoSets.
Logical database PNP/PNPCE* PCH PAP
Selection of Persons Objects from Personnel Planning Applicants
Infotypes that can be included in the InfoSet Infotypes for· Personnel Administration (0000-0999) · Time Management (2000-2999) · Payroll infotypes · Infotypes for Personnel Planning objects that can be related to persons If the object type is specified:· Infotypes for the object type · Infotypes for objects that can be related to the specified object typeIf the object type is not specified:· All infotypes · Infotypes for Recruitment (4000-4999)· Some infotypes for Personnel Administration (such as 0001 and 0002)
· Customer infotypes
Reporting examples · Selection of all persons who participated in a specific business event, output of prices for reserved business events · Selection of all persons assigned to a specific personnel area, output of qualifications held by these persons · Selection of all business events held in London in March, output of all persons who participated in these business events · Selection of all positions assigned to a specific organizational unit, output of all persons assigned to the positions · Selection of all applicants hired last year to work on special projects, output of addresses for the applicants selected
Logical database PNPCE (PNP Concurrent Employment) functions just like logical database PNP. The procedure for creating InfoSets is also the same. It only becomes significant if you work with Concurrent Employment.
Creating InfoSets
The maintenance procedure for HR InfoSets differs from the procedure described so far in this section inasmuch as HR data fields are grouped together in infotypes. To set up an InfoSet for the HR application, proceed as follows:
1. On the initial screen for maintaining InfoSets, enter a name for the InfoSet and choose Create.
2. On the next screen, enter a name for the InfoSet and select one of the HR logical databases in accordance with your reporting requirements.
Customer infotypes can be created on all HR logical databases. In each individual case, therefore, you must decide which database to select so that you can report on customer infotypes.
This screen enables you to enter an authorization group. All of the queries that are subsequently created using this InfoSet can only be executed by persons who have this authorization group.
3. Choose .
This takes you to the Infotype Selection for InfoSet screen. You now have the option of creating field groups and assigning fields as required for non-HR InfoSets. Field groups that correspond to infotypes and already contain fields, however, are always created for HR InfoSets. The field groups are displayed in an overview tree in the top right section of the screen.
The infotypes that you included in the InfoSet are displayed in an overview tree on the left of the screen. The infotype fields that are already included in field groups are displayed in a different color, and the corresponding field group ID is displayed.
In the standard system, a field group is created automatically for each infotype that you included in the InfoSet (a field group corresponds to an infotype).
In the standard system, each field group contains the infotype-specific fields. To ensure that working with the InfoSet is as easy as possible, you are advised to restrict your use of fields in each field group to those you really require. This means you should remove fields that are not required.
An infotype's fields must only be assigned to the pertinent field group. Make sure this assignment is correct. If the assignment is incorrect, the InfoSet could be rendered unusable.
When an InfoSet is created, the following fields are transferred automatically to the first field group:
§ Logical database PNPCE or PNP Personnel number
§ Logical database PAP Applicant number
§ Logical database PCH Object ID, plan version, and object type
6. Determine the fields that must be included in the field groups of your InfoSet. If you require further information, see Assigning Fields to a Field Group.
If you want, you can change the default sequence of field groups and fields as required using Drag&Drop.
7. To save the InfoSet, choose .
8. To generate the InfoSet, choose .
On the Change InfoSet (InfoSet name) screen, you can choose Edit ® Change infotype selection to add more infotypes to the InfoSet, or to remove infotypes from the InfoSet. Remember to regenerate the InfoSet afterwards.
This screen also enables you to update InfoSets if, for example, the system contains new additional fields for specific key values. To do so, choose InfoSet ® Additional functions ® Update additional HR fields.
9. Go back to the initial screen for InfoSet maintenance.
10. Choose User group assignment.
11. Select a user group, and save your entry.
sample code
START-OF-SELECTION.
GET pernr.
rp_provide_from_frst p0000 space pn-begda pn-endda.
if pnp-sw-found EQ '1'.
READ TABLE p0001 WITH KEY pernr = p0000-pernr.
if sy-subrc = 0.
write : p0001-plans. " earliest.
endif.
endif.
rp_provide_from_last p0014 space pn-begda pn-endda.
if pnp-sw-found EQ '1'.
READ TABLE p0014 WITH KEY pernr = p0000-pernr.
if sy-subrc = 0.
write : p0014-LGART. .
endif.
endif.

What is the difference between private API and public API??

Hi,
I came accross the terms private API and Public API ?
what are these APIs and what is the difference between them??
Thanks and Regards,
Soham

Soham,
Publicly Callable Business Process APIs are the list of supported and published APIs. Direct calls to any other routines are not supported, unless explicitly specified, because API validation and logic steps will be bypassed. Many other packages include procedures and functions, which may be called from the API code itself.
Note:216838.1 - Oracle HRMS Product Family Publicly Callable Business Process APIs (A Reference Consolidation)
Regards,
Greg

What is the difference between smart forms and scripts.?

what is the difference between smart forms and scripts.?

Differences between Smartforms and SAPscript
a) Multiple page formats are possible in smartforms which is not the case in SAPScripts
b) It is possible to have a smartform without a main window .
c) Routines can be written in smartforms tool.
d) Smartforms generates a function module when activated.
e) Smartforms can create web enable forms like XML
f) smartforms itself contine subroutine pools need not to main separetly like in case of scripts
Request you to refer the following links
www.sap-img.com/smartforms/smartform-sapscripts.htm
www.erpgenie.com/abap/smartforms_sapscript.htm
Sapscript vs Smartforms
Difference with SMARTFORMS vs. SapScript(SE71)
The Following are the differences :-
a) Multiple page formats are possible in smartforms which is not the case in SAPScripts
b) It is possible to have a smartform without a main window .
c) Labels cannot be created in smartforms.
d) Routines can be written in smartforms tool.
e) Smartforms generates a function module when activated
Scripts are client dependent whereas smartforms aren't.
Upto 99 main windows are possible in scripts and only one in smarforms.
To create multiple main windows in scripts, you just have to give the window type as MAIN whnever you create a window.
Scripts still exists but smartforms are in use from 4.6c version, now the lastest version of these two is adobe forms
SAP Smart Forms is introduced in SAP Basis Release 4.6C as the tool for creating and maintaining forms.SAP Smart Forms allow you to execute simple modifications to the form and in the form logic by using simple graphical tools; in 90% of all cases, this won't include any programming effort. Thus, a power user without any programming knowledge can
configure forms with data from an SAP System for the relevant business processes.
Advantages of SAP Smart Forms
SAP Smart Forms have the following advantages:
1. The adaptation of forms is supported to a large extent by graphic tools for layout and logic, so that no programming knowledge is necessary (at least 90% of all adjustments). Therefore, power user forms can also make configurations for your business processes with data from an SAP system. Consultants are only required in special cases.
2. Displaying table structures (dynamic framing of texts)
3. Output of background graphics, for form design in particular the use of templates which were scanned.
4. Colored output of texts
5. User-friendly and integrated Form Painter for the graphical design of forms
6. Graphical Table Painter for drawing tables
7. Reusing Font and paragraph formats in forms (Smart Styles)
8. Data interface in XML format (XML for Smart Forms, in short XSF)
9. Form translation is supported by standard translation tools
10. Flexible reuse of text modules
11. HTML output of forms (Basis release 6.10)
12. Interactive Web forms with input fields, pushbuttons, radio buttons, etc. (Basis-Release 6.10)
Reward Points if useful.

What is the difference between tkprof and explainplan

Hi,
what is the difference between tkprof and explainplan.

Execution Plans and the EXPLAIN PLAN Statement
Before the database server can execute a SQL statement, Oracle must first parse the statement and develop an execution plan. The execution plan is a task list of sorts that decomposes a potentially complex SQL operation into a series of basic data access operations. For example, a query against the dept table might have an execution plan that consists of an index lookup on the deptno index, followed by a table access by ROWID.
The EXPLAIN PLAN statement allows you to submit a SQL statement to Oracle and have the database prepare the execution plan for the statement without actually executing it. The execution plan is made available to you in the form of rows inserted into a special table called a plan table. You may query the rows in the plan table using ordinary SELECT statements in order to see the steps of the execution plan for the statement you explained. You may keep multiple execution plans in the plan table by assigning each a unique statement_id. Or you may choose to delete the rows from the plan table after you are finished looking at the execution plan. You can also roll back an EXPLAIN PLAN statement in order to remove the execution plan from the plan table.
The EXPLAIN PLAN statement runs very quickly, even if the statement being explained is a query that might run for hours. This is because the statement is simply parsed and its execution plan saved into the plan table. The actual statement is never executed by EXPLAIN PLAN. Along these same lines, if the statement being explained includes bind variables, the variables never need to actually be bound. The values that would be bound are not relevant since the statement is not actually executed.
You don’t need any special system privileges in order to use the EXPLAIN PLAN statement. However, you do need to have INSERT privileges on the plan table, and you must have sufficient privileges to execute the statement you are trying to explain. The one difference is that in order to explain a statement that involves views, you must have privileges on all of the tables that make up the view. If you don’t, you’ll get an “ORA-01039: insufficient privileges on underlying objects of the view” error.
The columns that make up the plan table are as follows:
Name Null? Type
STATEMENT_ID VARCHAR2(30)
TIMESTAMP DATE
REMARKS VARCHAR2(80)
OPERATION VARCHAR2(30)
OPTIONS VARCHAR2(30)
OBJECT_NODE VARCHAR2(128)
OBJECT_OWNER VARCHAR2(30)
OBJECT_NAME VARCHAR2(30)
OBJECT_INSTANCE NUMBER(38)
OBJECT_TYPE VARCHAR2(30)
OPTIMIZER VARCHAR2(255)
SEARCH_COLUMNS NUMBER
ID NUMBER(38)
PARENT_ID NUMBER(38)
POSITION NUMBER(38)
COST NUMBER(38)
CARDINALITY NUMBER(38)
BYTES NUMBER(38)
OTHER_TAG VARCHAR2(255)
PARTITION_START VARCHAR2(255)
PARTITION_STOP VARCHAR2(255)
PARTITION_ID NUMBER(38)
OTHER LONG
DISTRIBUTION VARCHAR2(30)
There are other ways to view execution plans besides issuing the EXPLAIN PLAN statement and querying the plan table. SQL*Plus can automatically display an execution plan after each statement is executed. Also, there are many GUI tools available that allow you to click on a SQL statement in the shared pool and view its execution plan. In addition, TKPROF can optionally include execution plans in its reports as well.
Trace Files and the TKPROF Utility
TKPROF is a utility that you invoke at the operating system level in order to analyze SQL trace files and generate reports that present the trace information in a readable form. Although the details of how you invoke TKPROF vary from one platform to the next, Oracle Corporation provides TKPROF with all releases of the database and the basic functionality is the same on all platforms.
The term trace file may be a bit confusing. More recent releases of the database offer a product called Oracle Trace Collection Services. Also, Net8 is capable of generating trace files. SQL trace files are entirely different. SQL trace is a facility that you enable or disable for individual database sessions or for the entire instance as a whole. When SQL trace is enabled for a database session, the Oracle server process handling that session writes detailed information about all database calls and operations to a trace file. Special database events may be set in order to cause Oracle to write even more specific information—such as the values of bind variables—into the trace file.
SQL trace files are text files that, strictly speaking, are human readable. However, they are extremely verbose, repetitive, and cryptic. For example, if an application opens a cursor and fetches 1000 rows from the cursor one row at a time, there will be over 1000 separate entries in the trace file.
TKPROF is a program that you invoke at the operating system command prompt in order to reformat the trace file into a format that is much easier to comprehend. Each SQL statement is displayed in the report, along with counts of how many times it was parsed, executed, and fetched. CPU time, elapsed time, logical reads, physical reads, and rows processed are also reported, along with information about recursion level and misses in the library cache. TKPROF can also optionally include the execution plan for each SQL statement in the report, along with counts of how many rows were processed at each step of the execution plan.
The SQL statements can be listed in a TKPROF report in the order of how much resource they used, if desired. Also, recursive SQL statements issued by the SYS user to manage the data dictionary can be included or excluded, and TKPROF can write SQL statements from the traced session into a spool file.
How EXPLAIN PLAN and TKPROF Aid in the Application Tuning Process
EXPLAIN PLAN and TKPROF are valuable tools in the tuning process. Tuning at the application level typically yields the most dramatic results, and these two tools can help with the tuning in many different ways.
EXPLAIN PLAN and TKPROF allow you to proactively tune an application while it is in development. It is relatively easy to enable SQL trace, run an application in a test environment, run TKPROF on the trace file, and review the output to determine if application or schema changes are called for. EXPLAIN PLAN is handy for evaluating individual SQL statements.
By reviewing execution plans, you can also validate the scalability of an application. If the database operations are dependent upon full table scans of tables that could grow quite large, then there may be scalability problems ahead. On the other hand, if large tables are accessed via selective indexes, then scalability may not be a problem.
EXPLAIN PLAN and TKPROF may also be used in an existing production environment in order to zero in on resource intensive operations and get insights into how the code may be optimized. TKPROF can further be used to quantify the resources required by specific database operations or application functions.
EXPLAIN PLAN is also handy for estimating resource requirements in advance. Suppose you have an ad hoc reporting request against a very large database. Running queries through EXPLAIN PLAN will let you determine in advance if the queries are feasible or if they will be resource intensive and will take unacceptably long to run.

What's the difference between Logic Studio 8 & 9?

Similar Messages

Maybe you are looking for