這套系是自己胡搞瞎搞下的產物,
本來的立意很偉大,
就是要把自己備份下來的DVD分享給大家,
除方便自己查詢,也免的忘記東西借給誰,
所以才有什麼,預借,確認借出,確認歸還的過程,
但之後的迴響卻不甚熱烈,
也或許是我程式沒寫好的原因吧!!
目前,JASONSEARCH將改為私人使用為主,
邏輯改為:開放,借出,鎖定,
開放即為”可借出的資料”,
借出即”可歸還的資料”,
鎖定為”不可借出,也不可歸還的資料”,
並將導入DW(資料倉儲)的概念,
明確的記錄資料的異動,
而不再只是簡單的異動查詢
寫完後,真覺得自己很偉大
(迷之聲:又在自HIGH了)
出現的訊息是
WORD無法讀取此文件。此文件可能已損壞。請試試看以下的方法：
*開啟並修復此檔案
*使用{文字復原}轉換程式來開啟此檔
解決的方式：「OFFICE2003請更新到SP2」
BO的報表,複雜的SQL開一個要1個半小時,
這樣算起來,一天還真的做不了幾張,
光看資料跑對不對一天就過了,
真傷工時呀!!
線上分析處理 ( On – Line Analytical Processing ; OLAP )
線上交易處理 ( On – Line Transaction Processing ; OLTP )
關聯式資料庫 ( Relational DataBase , RDB )
關鍵績效指標 ( Key Performance Indicator , KPI )
擷取、轉換並載入 (extract, transform, and load , ETL)
http://zh.wikipedia.org/wiki/ETL
維度 ( Dimension )
工作說明書 ( SOW )
別名 (一份基準表格):
別名是結構描述中現有表格的參照。
別名是以不同名稱完全複製自原始表格 (基準表格) 的表格。
表格中的資料完全與原始表格相同，
但是不同的名稱會「欺騙」查詢的 SQL，
讓它以為您使用的是兩個不同的表格而接受。
本文 (已定義的連接路徑):
本文是連接的集合，
提供 Web Intelligence 有效的查詢路徑以產生 SQL。
捷徑連接:
捷徑連接是一個可提供兩個表格之間替代路徑的連接。
由於不考慮中介表格並將一般較長的連接路徑縮短，
因此捷徑連接能夠改善查詢的效能。
捷徑連接最常用來將一個共用查詢表格沿著連接路徑進一步連結到另一個表格。
連接路徑是由同一個本文中許多不同的表格所構成。
此時，捷徑連接只有在被查詢的值於表格階層中解除常態化成較低層級，
使得相連的所有層級都存在相同的值時才有效。
連接問題:
Loop / 多對單一查詢設陷 (收斂式多對單一連接) / 一對多重查詢設陷 (序列式多對單一連接)
MT/DIM
DIM_CURRENT/DIM_OLD/DIM_TEMP
TRUNCATE tmp –> INNER JOIN比對,如完全一樣INSERT tmp
1–> 上END DATE, UPDATE ( END_DATE IS NULL and _tmp no data )
2–> INSERT ( select _current and _tmp not exits )
MT/FCT
串SK & measure出來的值
MT/REF
PK,部分功能同DIM
INIT
建初始 @
EL
SP_EL_DIM_IMPORT.sql
–STEP 1: DROP COLUMN EXT_DATE
–STEP 2: EMPTY EL_TABLE
–STEP 3: CREATE BULK INSERT STATEMENT
–STEP 4: EXECUTE BULK INSERT STATEMENT
–STEP 5: ADD COLUMN EXT_DATE
–STEP 6: UPDATE EXT_DATE資料提供：BOP\BOP_DW\BI_TXT\
自行產生：BOP\BOP_DW\DIM_TXT\
DDL
Creat Table
笛卡兒乘積是一個結果集，內含查詢中每個表格每一列的所有可能組
合。笛卡兒乘積幾乎都是不正確的結果。
兩個表格在結合時，不指定任何條件，如：
SELECT employee.realname, salary.amount FROM employee, salary
SELECT employee.realname, salary.amount FROM employee JOIN salary
SELECT employee.realname, salary.amount FROM employee CROSS JOIN salary
在這個例子中，employee 原有 4 筆資料，而 salary 有 5 筆資料，在 JOIN 之後，
結果將是兩者資料筆數的乘積：20。
就等於是將兩個資料表中，所有可能的組合全部列出來一樣，
其結果在實務上不見得有意義。這種結合可被視為兩個資料表的
「笛卡兒乘積（Cartesian product）」。
在“漢化新世紀”中，漢化作者是這樣描述BlackICE的：
“該軟體在九九年穫得了PC Magazine 的技術卓越大獎，專家對它的評語是‘對於沒有防火牆的家庭用戶來說，BlackICE是一道不可缺少的防線；而對於企業網路，它又增加了一層保護措施–它並不是要取代防火牆，而是阻止企圖穿過防火牆的入侵者’BlackICE集成有非常強大的偵測和分析引擎，可以識別 200 多種入侵技巧，給你全面的網路偵測以及系統防護，它還能即時監測網路連接埠和協議，攔截所有可疑的網路入侵，無論駭客如何費盡心機也無法危害到你的系統。而且它還可以將查明那些試圖入侵的駭客的NetBIOS(WINS)名、DNS名或是他目前所使用的IP地址記錄下來，以便你采取進一步行動。封言用過後感覺，該軟體的靈敏度和準確率非常高，穩定性也相當出色，系統資源佔用率極少，是每一位上網朋友的最佳選擇。”
閱讀全文 “[轉貼]BlackICE”
What is a universe?
A universe is a file that contains the following:
• Connection parameters for one or more database middleware.
• SQL structures called objects that map to actual SQL structures in the database such as columns, tables, and database functions. Objects are grouped into classes. Objects and classes are both visible to Web Intelligence users.
• A schema of the tables and joins used in the database. Objects are built from the database structures that you include in your schema. The schema is only available to Designer users. It is not visible to Web Intelligence and Desktop Intelligence users.
Web Intelligence users connect to a universe, and run queries against a database. They can do data analysis and create reports using the objects in a universe, without seeing, or having to know anything about, the underlying data structures in the database.
What is the role of a universe?
The role of a universe is to provide an easy to use and understand interface for non technical Web Intelligence users to run queries against a database to create reports and perform data analysis.
As the universe designer, you use Designer to create objects that represent database structures, for example columns and database functions, that users need to access and query, to get the information necessary to meet their business requirements. The objects that you create in the universe must be relevant to the end user business environment and vocabulary. Their role is to present a business focussed front end to the SQL structures in the database.
The following diagram shows the role of objects as the mapping layer between a database schema and the Query work area in Web Intelligence, that users use to create queries to run against database tables.
What does a universe contain?
A universe contains the following structures:
• Classes
• Objects
Classes
A class is a logical grouping of objects within a universe. It represents a
category of objects. The name of a class should indicate the category of the
objects that it contains. A class can be divided hierarchically into subclasses.
Objects
An object is a named component that maps to data or a derivation of data in
the database. The name of an object should be drawn from the business
vocabulary of the targeted user group. For example, objects used in a
universe used by a product manager could be Product, Life Cycle, or Release
Date. A universe used by a financial analyst could contain objects such as
Profit Margin, and Return on Investment.
Types of objects
In Designer, objects are qualified as one of three types: dimension, detail, or
measure.
- Dimension –> Parameters for analysis. Dimensions typically relate to a
hierarchy such as geography, product, or time. For example
Last Name and City_Id- Detail –> Provide a description of a dimension, but are not the focus
for analysis. For example Phone Number- Measure –> Convey numeric information which is used to quantify a
dimension object. For example Sales Revenue
Objects infer SQL structures displayed in a schema
The objects that Web Intelligence users see in a universe infer SQL
structures that you have inserted into a database schema. You, as the
universe designer, create this schema based on the tables and joins that are
required to return the data, needed by users for their analysis and report
creation.
The schema is a part of the universe file, but is only visible and accessible in
Designer.