Have u ever thought why we start and stop SAS & SAW in defined orders???

Hi again.....

Did this thing ever come into ur mind that why we stop SAS(Siebel Analytics Server) & SAW(Siebel Web Server) in a defined order???
Well it came into my mind... And here is the reason why..

Well first lets talk of whts the order of starting and stopping the SAS & SAW Servers...
Start
SAS -> SAW
Stop
SAW-> SAS

Implicit Fact Column in the Admin Tool

Many a times i have heard users facing issues with server picking up improper joins in Admin tool. Lets take an example to understand this and lets c the solution....


Take an example that we have 2 dimension tables viz. Day Dim & Opty Dim and 2 fact tables viz. Revenue Fact & Order Fact. Now, I wana make my report in such a manner where i take only 2 dimension columns from the 2 dim tables and no fact column eg: I wana c number of opptys in an year.

What will happen???

Connection Pool in Admin Tool....

Hi All,

m back again after some gap... Lets understand whts connection pool..


The connection pool is an object in the Physical layer that describes access to the data source. It contains information about the connection between the Siebel Analytics Server and that data source. 

The Physical layer in the Administration Tool contains at least one connection pool for each database. When you create the physical layer by importing a schema for a data source, the connection pool is created automatically. You can configure multiple connection pools for a database. Connection pools allow multiple concurrent data source requests (queries) to share a single database connection, reducing the overhead of connecting to a database.

For each connection pool, you must specify the maximum number of concurrent connections allowed. After this limit is reached, the Analytics Server routes all other connection requests to another connection pool or, if no other connection pools exist, the connection request waits until a connection becomes available.