System Testing :  This is the iterative process. The focus 
is to to get the correct answer or effective answer.This is 
done after the Unit test is carried out.
  Some cross module errors could also be resolved at this 
stage.  Post analysis the necessary corrections to the 
components are made and finaaly the modules are successfull 
system tested when the errors are non-existent or 
negligible.

Integration Testing :  This is the final stage as all the 
errors are removed almost and is at the final stage, so 
here we concentrate on integrateing the results across 
modules. performance of the etl is tested.
   Any new answers are pls provide

clients side cliams are only about the report specification

The fact which is not having any measures(like Quantity) 
are called factless fact .To track the events (like Bad 
order )the factless fact are used in the Projects

to combine two diffeerent diminsions information we use 
fact less fact table.
for ex:if we want to get deatails about a promotion 
information like when it is lauched.we will get that 
information from promotion dimensions and time 
dimension ,so in this scenerio there is no need of any fact 
information but we need data from thes two dimension then 
we go for factless fact table

Factless Fact is having only dimensionla keys with no 
measures.Its basically only to get information and no 
calculations involved.
For eg:how many no. of Policy closed last month

we might say Factless Fact Table basically used to support 
negative analysis report

In Schema level we can say as when we consider these as 
Count of Occurances/even that does not involved or getting 
aggreaged at the fact table means,we call these fact(has no 
measure but with events/occurance) called as Fact less Fact 
table.

for eg. No :of Accident for a Months
           No : of Policy has been closed this months.

Generally we  using the factless fact when we want events 
that happen only at information level but not included in 
the calculations level.just an information about an event 
that happen over a period.
Factless fact tables are used for tracking a process or 
collecting stats. They are called so because, the fact 
table does not have aggregatable numeric values or 
information. They are mere key values with reference to the 
dimensions from which the stats can be collected.

A second kind of factless fact table is called a coverage 
table. A typical coverage table is Coverage tables are 
frequently needed when a primary fact table in a 
dimensional data warehouse is sparse. Figure 2 also shows a 
simple sales fact table that records the sales of products 
in stores on particular days under each promotion 
condition. The sales fact table does answer many 
interesting questions but cannot answer questions about 
things that didn't happen. For instance, it cannot answer 
the question, "Which products were on promotion that didn't 
sell?" because it contains only the records of products 
that did sell. The coverage table comes to the rescue. A 
record is placed in the coverage table for each product in 
each store that is on promotion in each time period. Notice 
that you need the full generality of a fact table to record 
which products are on promotion. In general, which products 
are on promotion varies by all of the dimensions of 
product, store, promotion, and time. This complex many-to-
many relationship must be expressed as a fact table. This 
is one of Kimball's Laws: Every many-to-many relationship 
is a fact table, by definition.

A cube contains data in multi dimensional analyized format.
And it's components are :
1) Measure / Fact :- It's an object which is been analyized.
2) Dimension      :- It's an object with respect to which we
perform Analysis.
3) Detailed       :- It's an object which provide extra
information about a dimension.
in BOXI A cube is called Micro Cube.

Micro Cube is a processing Unit. It Composed facts & 
Diamensions & measures. 
 Micro Cube is cleared by using "Purge" Option.

i think 
if  you want to text the records from  one table 
that time you can go to session properties and select text 
load option and give number like how many rows you want to 
test(ex: 10)
after completion of the session you cant able to see the 
tested records in your target table

you would get o/p like:  no rows should be selected

I think it's not text load, rather it is TEST LOAD

using the informatica schedular tool or third party tools 
like control m, maestro, tivoli etc. if wrong sorry

u can use autosys scheduler,or workflow manager in 
informatica

scheduling is an administrative tool to perform to run the
session at a specific time and date. if wrong pls inform it

Informatica has own Sheduling components .Since Informatica 
widely used as Data integration and Data warehousing Entity 
and there are lots of depedencies on other jobs ,reason 
informat application is scheduled by external sheduluing 
device such as
1) Control M
2) Crontab 
3) maestro

Basic Functionlity behind scheduling is PMCMD cmd thro 
shell scripts they trigger informatica jobs via pmcmd 
command.

Do one thing Upgradation of repository means u can upgrade 
the lower version into higher version tis u can do in 
Repository Manager right click on that there is the option 
upgrade select that and then add the licence & product 
code......

Cognos8 has analysis studio,event studio,metric studio 
report net don't.In report net we can not view 
multidimensional.Some new templates added to the cognos8.

Every one has its own Importence,
Every one will Dependent on other one,

Choose The Carrier as a Jnuior Role,,,,

join problems are analysed by Integrity checking and
resolve by setting cardinalities

join problems can be analised by doing chek 
integrity& "Detect joins " option also.

To solve the join path problems using cardinalities also

Join problem by setting cardinality

We have to crate 60535 repositories in Informatica. 
Acctually we have min port no is 5001,max-65535 so each 
port no contain one repository in Informatica, any version 
of Informatica.each repository will maintain one port no.

This is the correct answer.

We can create any no. of repositories in Informatica Under 
one server .As per my knowledge there is no limit .

In Windows we can create only one Repositor.
We may create more than one in unix\Linux Platforms.
(What i Read i am giving)

We can create any no. of repositories in Informatica Under
one server. You can install one Repository Server on a
Windows machine

In Informatica Power mart we can create any no of 
repositories , but we can not share the matadata accross 
the repositories, 

In Informatica Power center we can create any no of 
repositories , but we can disignate only one repository as 
a global  repository which can access or share matadata 
from all other repositories

Any No of Repo v can create only thing is ur db user name n 
connect string should be differ.
n u can make them global also
(telling this by personal exp, as I have created 2 repo 
both as a globla repo)

to use the permanent format catalog the statement is

libname a 'c:\sas\files';
options fmtsearch=(a.treesfmt);
proc print data=a.trees (obs=5) label; 
run;

To use your permanent sas data set eith user-defined 
fortmat for the future sas sessions you need to

1. assign a sas library to location of the sas format 
catalog.
2. specfiy the name of the sas format catalog with the ftm 
seacrch option.


for info this website  
http://www.umass.edu/statdata/software/handouts/SASLevel2.pd
f

Hi Diya! Thanks for your valuable answer. I shall start to
work with this.
Thank you.

Tanks diya... it works.

1.) 
we can distinguish between unique and duplicate records in 
informatica by using forward reference  technique , 
in the sense , we can store the previous rec key value in 
Variable_Port and can be compared with the previous rec key 
value , but Data has to be come in sorted order on that key 
column , for that we should use sorter transformation.

once if you find the duplicate rec by comparing , you can 
flag  that rec as dulicate and you can divert it to other 
target.

2.) with out using sorter 

in order to collect only unique records for flat file , 
just use aggregator before exp transformation, and check 
group by on the key column where you are expecting 
duplicate records. so you will get only unique records and 
duplicate records will be eliminated.

once check out with ur transformations , the output ports
should generate the proper data as per the given conditions

once check out your output ports and input ports and the 
pipeline between

example:consider a product example car and the ways 
received orders.
product name            order method
maruthi                  telephone booking
alto                     telephone booking 
Mercedez                 telephone booking
maruthi                  fax booking
maruthi                  agent
.....

so when you do sliciing and dicing  if you want to display 
all the products sold through internet it will display all  
product sold by internet booking.ie viewing the data in 
different prespectives. we basically use this concept while 
dealing with cubes.

Slicing is a vertical view of a report and 
dicing is a horizontal view of a report. simple....