Difference between materailized view and a table

hey hiii
i want to know what is a difference between a materialized view and a table i.e suppose i create a table A and another table B on table A i have created a trigger which will upload all the changes made in A ie insert,update or delete so whether this will perform all the action that a materialized view can perform on A or is there any difference between them
thks

I'll add to Nicolas' answer that the MV maintenance does have access to mechsnisms other than row-by-row replication of the trigger-based type. Direct path inserts to the base table are very efficiently propagated to the MV, as are partition-based DDL operations. Also MV's come with optional query rewrite built in (you need 10g+ to query rewrite to a non-MV data set), and scheduled refresh so you can defer maintenance of the data set until later.
MV maintenance can be less efficient though -- you may know something about the data and the way that it changes that allows you to write more efficient meintenance than the MV code.

Similar Messages

Difference between Database view and Table

Hi there,
Can anyone tell me the difference between Database view and Table.
Will the Database view query be more faster than a database table?

Tables and database views can be defined in the ABAP Dictionary.
These objects are created in the underlying database with this definition. Changes in the definition of a table or database view are also automatically made in the database.
Data from several tables can be combined in a meaningful way using a view (join).
You can also hide information that is of no interest to you (projection) or only display
those data records that satisfy certain conditions (selection).
Database views implement an inner join. You only get those records which have an
entry in all the tables included in the view.
in views db modifications are not possible
views only contain data at run time
when they consult the database
in case of views the join definitions are already sstored in the database itself
whereas join as open sql is a query to oracle database as similar select statements
Views are optimized by SAP and stored in the repository while Joins
are in reports that needs to be compiled at every execution
Reward if helps
Regards,
Senthil
Message was edited by: senthil kumar

Hi, difference between database view and elementary search help

hi
pl. can any one tell me the difference between
database view and elementary search help,
and help view and elementary search help,
and database view and help view.
in the output i do not see any difference.
thanx.
rocky robo

HI
An entire table can be included in a database view. In this case all the fields of the included table will become fields of the view (whereby you can explicitly exclude certain fields). If new fields are included in the table or existing fields are deleted, the view is automatically adjusted to this change.
Database view:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/36/74c0358373003ee10000009b38f839/frameset.htm">http://help.sap.com/saphelp_nw04/helpdata/en/36/74c0358373003ee10000009b38f839/frameset.htm</a>
Elementary search help:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee38446011d189700000e8322d00/frameset.htm">http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee38446011d189700000e8322d00/frameset.htm</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/8b/415d363640933fe10000009b38f839/frameset.htm">http://help.sap.com/saphelp_nw04/helpdata/en/8b/415d363640933fe10000009b38f839/frameset.htm</a>
Help view:
Help views are used if a view with an outer join is needed as selection method in a search help.
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/42/81c1351181b73fe10000009b38f839/frameset.htm">http://help.sap.com/saphelp_nw04/helpdata/en/42/81c1351181b73fe10000009b38f839/frameset.htm</a>
Regards,
Gunasree

Difference between Data staging and Dimension Table ?

Difference between Data staging and Dimension Table ?

Data Staging:
Data extraction and transformation is done here.
Meaning that, if we have source data in flat file, we extract it and load into staging tables, we take care of nulls, we change datetime format etc.. and after such cleansing/transformation at then end, load it to Dim/Fact tables
Pros: Makes process simpler and easy and also we can keep track of data as we have data in staging
Cons: Staging tables need space hence need memory space
Dimension Table:
tables which describes/stores the attribute about specific objects
Below is star schema which has dimension storing information related to Product, Customer etc..
-Vaibhav Chaudhari

Difference between line type and internal table?

Hi..
I wanted to know, what is the difference between Line type and Internal Table?

Hi,
Before the 4.7 release in SAP if we want to define an internal table we have to write the defination using the occurs statement and we need to define all the fields using INCLUDE STRUCTURE or indidually all the fields ine by one.
From 4.7 release of R/3 SAP introduced the Line type concept and it's part of the ABAP OOPS concept. for internal table defination we don't need to use the occur statements. Instead INCLUDE structure we need to create a Line type for that structure in Se11 and then we can define the internal table like :
DATA : ITAB TYPE TABLE OF <LINE_TYPE>.
Only thing is this table will be a table without header. So for internal table processing we need to define a work area structure of type line of line type . EX:
DATA: WA_ITAB TYPE LINE OF <LINE_TYPE>.
Hope this helps.
Thanks,
Greetson

Difference between work area and internal tables.

Hi I wanna know the difference between work area and internal tables.
what happend if i give with out header line in internal table.
also how to assosiate work area to internal table in that scenario.

Hi Balaji..
The internal table is an ABAP runtime object which has two parts the Body and the header.
Whereas a work area cannot have a body.. It is mere a field or group of fields which can hold values at runtime..
In the SAP higher versions mySAP ERP, the use of tables with header line is made obsolete.. But there is absolutely no problem with the same..
Just think that when you define an internal table with occurs or with header line statement, the system automatically creates a workarea with this table, using which you can access the contents in the bosy of tyhe table.. You can read a record from the table body to this header or add a record in the header to the internal table body..
When you work with a table ITAB without a header line, you can not use statements like READ TABLE, APPEND, INSERT etc without giving an explicit work area..
Suppose i have an internal table like:
DATA : itab TYPE STANDARD TABLE OF t001.
This table will not have a header with it.
If you will use APPEND itab. The compilor will give error.
Here i will create a work area with same structure of the table.
DATA : e_wa TYPE t001.
Now i will write:
APPEND e_wa TO itab.
READ TABLE itab INTO e_wa WITH KEY xxxxxx
LOOP AT itab INTO e_wa... etc..
In a better approach we use Field symbols with such tables, instead of structures
FIELD-SYMBOLS: <fs_itab> TYPE t001.
So,
LOOP AT itab ASSIGNING <fs_itab>
READ TABLE itab ASSIGNING <fs_itab> etc.. However we can not use field symbols in few cases..
I hope this will help you..
Thanks and Best Regards,
Vikas Bittera.
**Points for usefull answers**

What is the difference between standard,sorted and hash table

<b>can anyone say what is the difference between standard,sorted and hash tabl</b>

Hi,
Standard Tables:
Standard tables have a linear index. You can access them using either the index or the key. If you use the key, the response time is in linear relationship to the number of table entries. The key of a standard table is always non-unique, and you may not include any specification for the uniqueness in the table definition.
This table type is particularly appropriate if you want to address individual table entries using the index. This is the quickest way to access table entries. To fill a standard table, append lines using the (APPEND) statement. You should read, modify and delete lines by referring to the index (INDEX option with the relevant ABAP command). The response time for accessing a standard table is in linear relation to the number of table entries. If you need to use key access, standard tables are appropriate if you can fill and process the table in separate steps. For example, you can fill a standard table by appending records and then sort it. If you then use key access with the binary search option (BINARY), the response time is in logarithmic relation to
the number of table entries.
Sorted Tables:
Sorted tables are always saved correctly sorted by key. They also have a linear key, and, like standard tables, you can access them using either the table index or the key. When you use the key, the response time is in logarithmic relationship to the number of table entries, since the system uses a binary search. The key of a sorted table can be either unique, or non-unique, and you must specify either UNIQUE or NON-UNIQUE in the table definition. Standard tables and sorted tables both belong to the generic group index tables.
This table type is particularly suitable if you want the table to be sorted while you are still adding entries to it. You fill the table using the (INSERT) statement, according to the sort sequence defined in the table key. Table entries that do not fit are recognised before they are inserted. The response time for access using the key is in logarithmic relation to the number of
table entries, since the system automatically uses a binary search. Sorted tables are appropriate for partially sequential processing in a LOOP, as long as the WHERE condition contains the beginning of the table key.
Hashed Tables:
Hashes tables have no internal linear index. You can only access hashed tables by specifying the key. The response time is constant, regardless of the number of table entries, since the search uses a hash algorithm. The key of a hashed table must be unique, and you must specify UNIQUE in the table definition.
This table type is particularly suitable if you want mainly to use key access for table entries. You cannot access hashed tables using the index. When you use key access, the response time remains constant, regardless of the number of table entries. As with database tables, the key of a hashed table is always unique. Hashed tables are therefore a useful way of constructing and
using internal tables that are similar to database tables.
Regards,
Ferry Lianto

What is the differences between Transparent,Pooled and Cluster tables?

Hello all,
What is Pool table?What is the differences between Transparent,Pooled and Cluster tables?
Regards!
Purna

Transparent table:
Tables can be defined independently of the database in the ABAP Dictionary. The fields of the table are defined together with their (database-independent) data types and lengths.
A table definition in the ABAP Dictionary has the following components:
Table fields: The field names and the data types of the fields contained in the table are defined here.
Foreign keys: The foreign keys define the relationships between this table and other tables.
Technical settings: The technical settings define how the table is created on the database.
Indexes: Indexes can be defined for the table to speed up data selection from the table.
There are three categories of database tables in the ABAP Dictionary.
A physical table definition is created in the database for the table definition stored in the ABAP Dictionary for transparent tables when the table is activated. The table definition is translated from the ABAP Dictionary to a definition of the particular database.
On the other hand, pooled tables and cluster tables are not created in the database. The data of these tables is stored in the corresponding table pool or table cluster. It is not necessary to create indexes and technical settings for pooled and cluster tables.
Pooled table
Pooled tables can be used to store control data (e.g. screen sequences, program parameters or temporary data). Several pooled tables can be combined to form a table pool. The table pool corresponds to a physical table on the database in which all the records of the allocated pooled tables are stored.
Cluster table
Cluster tables contain continuous text, for example, documentation. Several cluster tables can be combined to form a table cluster. Several logical lines of different tables are combined to form a physical record in this table type. This permits object-by-object storage or object-by-object access. In order to combine tables in clusters, at least parts of the keys must agree. Several cluster tables are stored in one corresponding table on the database.
Regds,
Manohar

Difference between interface view and interface controller

Hi,
What is the difference between interface controller and interface view?
When we will use interface controller and when we will use interface view?
How do we create an interface view?
How do we attach this interface view to a view in another component
Regards
MQ

Hi
Interface View Controllers
A) Implement event handlers which are called when ..
-starting (start-up plugs) Web Dypro applications
-a component is reached via navigation (inbound plugs)
B) Allow fireing outbound plugs (navigation)
C) Allow firing exit plug
D) Have no own context, public methods or events
Interface Controller of a Component
The interface controller of a Web Dynpro component contains all context nodes, events and methods of the component controller to which you assigned the Interface addition in the Controller Editor. These parts can be displayed in the interface controller view, although you cannot edit them here.
Interface Controller of a Component Interface
A Web Dynpro component interface can be created independently and defined so that it can be implemented later in any components (see working with Web Dynpro Component Interfaces in the Programming Manual of this documentation). That is why in this case you can define the context nodes, methods and events you require in the interface controller view. The relevant implementation then takes place in the component controller of the implementing component.
Check this links and work on it.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/28113de9-0601-0010-71a3-c87806865f26?rid=/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d#13 [original link is broken]
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/28113de9-0601-0010-71a3-c87806865f26?rid=/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d#12 [original link is broken]
Interface view and interface controller
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f727d100-0801-0010-4cbd-b0ad5c161945
Difference between custom controller and interface component
Thanks and Regards,
Tulasi Palnati

Wrong position of objects / difference between editor view and browser view.

Dear Adobe
System info: Mac OS X 10.9, Muse 7.1 Build 329, Chrome, Safari and Firefox in the newest versions.
I use Muse since version 5 and this effect does exist 'til today (v7.1) without any changes.
Many times i have differences in the position of placed objects. But this missbehaviour is not realy logical. For example take a look to this illustration:
Left: Muse Editor, right: Browser (in this case its chrome, but the effect is identical in safari and firefox too)
Left you see one pixel space between the blue bar and the shadow (image-object). In the browser is the space bigger (2px). When i move the shadow-object in muse one pixel higher, then look this so:
The shadow is now within the bluebar. The position has changed in muse for 1 pixel, in browser around 7 pixels... i don't see, why.
Another example:
Left Muse Editor, right Browser... do you see the dramatic difference between?
I hope, this problem can be solved with a future version...
Best regards
Michael

This variation is due to the difference in the layout of text between Design view and Preview, which is representative of the variations that exist between browsers, OSes, devices and individual versions of each of those.
It's impossible to reverse engineer the structure of the objects from the screenshots, but how the objects or individual sized and positioned relative to one another is key to understanding (and explaining) what you're encountering.
If you provide the URL for this page I'll attempt take a look at it and provide some guidance for how to achieve the effect you're looking for within the constraints inherent in working with live text on the web.
(In case you're not already aware, you can Publish to a free trial site on Adobe Business Catalyst at any time using the Publish button. Using trial sites on BC is very convenient, even if you don't plan to host the finished site on BC.)

Differences Between Entry View and GL View - Doc. Splitting

Hello Experts,
I need some help about an issue occuring in our Client right now, differences in Entry view and GL View. Any help will be appreciated.
- Debit or Credit Balance posting of an account does not match with the balance posted in GL View, generally the GL view posts an amount above of the Entry view, and then it cause the Debit/Credit balance does not match with the movement in Entry View. Example Below from Quality System:
Debit Balance in January 2013: 319.794.641,38
Movement from FAGLL03 - OK.
Movement from FBL3N - Entry View Difference: 319.794.619,86 - 319.794,641,38 = 21,52 Debit
Checking NEW-GL Movement, we found the posting difference:
The Document Entry View: 5.465,22 Credit From Bank Account
The GL View - SAP Credited 5.486,74 Bank Account PC 1411 and Cr Bank Account PC 1444.
Total: -5.486,74 + 21,52 = 5.465,22 OK on Balance, but not OK from movement considering the Entry view.
- Questions:
- I understood the calculations, it was calculated as mentioned in note 1072850_Field overflow or very large amounts due to doc splitting
- Is this supposed to happen by SAP Doc.Splitting perspective?
- I am facing this issue because we need to send to the government account balances and their movements, and according to laws we need to pay additional amount for addtional lines generated, so it was better to send the information based in Entry View, not in GL View.
- FS10N Show warning message "New general Ledger Implemented, use FAGLB03", and when i execute the transaction the balance showed was the balance from FAGLB03.
- SAP 605 APPL.
Regards,
Leandro.

Hi ,
Can you Please look at OSS note
1655571 - Multiple values and multiple/additional line items appearing in the NewGL View when compared to Entry View
Many Thanks

Difference between INLINE view and WITH clause

Can anyone plz explain me about the performance difference between the below queries?
Query using INLINE view:
SELECT e.ename AS employee_name,
dc.dept_count AS emp_dept_count
FROM emp e,
(SELECT deptno, COUNT(*) AS dept_count
FROM emp
GROUP BY deptno) dc
WHERE e.deptno = dc.deptno;
Query using WITH clause:
WITH dept_count AS (
SELECT deptno, COUNT(*) AS dept_count
FROM emp
GROUP BY deptno)
SELECT e.ename AS employee_name,
dc.dept_count AS emp_dept_count
FROM emp e,
dept_count dc
WHERE e.deptno = dc.deptno;

Here's another one:
http://www.oracle-base.com/articles/misc/WithClause.php
And, here on this forum you will see that the WITH-clause is heavily used by all of us in order to generate some sample data (when OP's don't care to post CREATE TABLE + INSERT INTO statements).
The WITH clause enables you as well to 'pretend' you have a table and demonstrate a solution very quickly, without doing actual DDL .
As for the performance difference:
We would need to know your database version and many other things.
See:
HOW TO: Post a SQL statement tuning request - template posting
for step by step instructions you can (and should) explore yourself.

Creating a master-detail relation between a view and a table

Hi all,
I have a problem with creating a master-detail relation between a database-view with lots of customer data and a small table with per customer a list of entities of our companies who may work for that customer.
Somehow I seem to be unable to create a relation between these two. I can't find where I can make a foreign key using Toplink to implement the relationship. And neither can I get a Viewlink object doing the job using ADF Business Components.
Somebody any suggestions on this problems?
Regards,
Birgit

There is a key relationship between two fields which form the primary key in the main table of the view and two fields in the second table.
I created a viewlink manually, but I still couldn't get the data correct i.e. a form with one record of a customer from the main view and a small table with all entities of our company who can make performances for that customer.
I tried to find a manual or a how-to on this topic but I didn't find anything helpfull yet.
Regards,
Birgit
After a couple more tries, I got the master-detail working. With all the fiddling I am not sure what caused the problem but I think the finally action was checking which fields of the view were marked as primary keys.
Now everthing is up and running.
Birgit
Message was edited by:
user492355

Difference between inline view and WITH

All,
What is the difference between an inline view and a query using 'with' keyword...? (scenario / example will be more helpful)

Thank-you ajay. below section was really helpful, in the above link.
big_table@ORA920> set echo on
big_table@ORA920> set autotrace on statistics
big_table@ORA920>
big_table@ORA920> with owners
2 as
3 ( select distinct owner username from all_objects )
4 select count(*)
5 from all_objects, owners
6 where all_objects.owner = owners.username
7 union all
8 select count(*)
9 from dba_objects, owners
10 where dba_objects.owner = owners.username
11 /
COUNT(*)
30537
30977
2 rows selected.
Statistics
4 recursive calls
7 db block gets
302441 consistent gets
1 physical reads
520 redo size
418 bytes sent via SQL*Net to client
499 bytes received via SQL*Net from client
2 SQL*Net roundtrips to/from client
3 sorts (memory)
0 sorts (disk)
2 rows processed
big_table@ORA920>
big_table@ORA920> select count(*)
2 from all_objects, (select distinct owner username from all_objects ) owners
3 where all_objects.owner = owners.username
4 union all
5 select count(*)
6 from dba_objects, (select distinct owner username from all_objects ) owners
7 where dba_objects.owner = owners.username
8 /
COUNT(*)
30537
30977
2 rows selected.
Statistics
28 recursive calls
0 db block gets
442058 consistent gets
0 physical reads
0 redo size
418 bytes sent via SQL*Net to client
499 bytes received via SQL*Net from client
2 SQL*Net roundtrips to/from client
4 sorts (memory)
0 sorts (disk)
2 rows processed
big_table@ORA920> set autotrace off
Edited by: sikander on Sep 9, 2010 12:39 AM
Edited by: sikander on Sep 9, 2010 12:40 AM

What is the difference between Saved views and queries

Hi all,
Just i want to know the difference between 2 options in the Bex Analyzer. Those options are "Queries" and " Saved Views". Please check it out and let me know the difference

To add to the previous posts, saved views can also be useful when developing web templates. You can create and save one query and then save a number of views from this query, with different layouts, filters etc. web templated can then be developed using the saved views. BW 2004s introduces a whole load of standard functions to switch dataproviders in web templates. Thes can be used to switch between a number of views in a template. I have used this to present selections of key figures, switch navigation states etc.
Regards
Peter

Difference between materailized view and a table

Similar Messages

Maybe you are looking for