Configuring a scalable shared database requires that the storage area network environment is already working properly 配置可縮放共享數(shù)據(jù)庫要求存儲(chǔ)區(qū)域網(wǎng)絡(luò)環(huán)境正常運(yùn)行。
Updating a scalable shared database involves a three - phase update cycle , which begins with the detach phase 更新可縮放共享數(shù)據(jù)庫涉及一個(gè)以分離階段開始的三階段更新循環(huán)。
The attach phase in the figure illustrates making the reporting database available as a scalable shared database 此圖中的附加階段說明如何將報(bào)表數(shù)據(jù)庫用作可縮放共享數(shù)據(jù)庫。
On being detached from the last server instance , the reporting database ceases being a scalable shared database 當(dāng)報(bào)表數(shù)據(jù)庫從最后一個(gè)服務(wù)器實(shí)例分離時(shí),便停止用作可縮放共享數(shù)據(jù)庫。
The life of a scalable shared database begins by building a new reporting database on a set of reporting volumes 可縮放共享數(shù)據(jù)庫的生存時(shí)期開始于針對(duì)一個(gè)報(bào)表卷集生成新的報(bào)表數(shù)據(jù)庫。
To ensure that your environment supports scalable shared databases , we recommend that you adhere to the following guidelines 為了確保您的環(huán)境支持可縮放共享數(shù)據(jù)庫,建議您遵守下列準(zhǔn)則:
This topic describes how to build or refresh a reporting database that is intended for use as a scalable shared database 本主題說明了如何生成或刷新要用作可縮放共享數(shù)據(jù)庫的報(bào)表數(shù)據(jù)庫。
To maximize availability of a scalable shared database configuration , you can use two , alternate sets of reporting volumes 為了最大限度地利用可縮放共享數(shù)據(jù)庫配置,可以交替使用兩組報(bào)表卷。
Once established as a scalable shared database , a reporting database can be shared by clients using different reporting servers 將報(bào)表數(shù)據(jù)庫作為可縮放共享數(shù)據(jù)庫建立后,使用不同報(bào)表服務(wù)器的客戶端便可共享此數(shù)據(jù)庫。
When this process is completed on a given reporting server , the reporting database becomes a scalable shared database on that server 在給定的報(bào)表服務(wù)器中完成此過程后,該服務(wù)器中的報(bào)表數(shù)據(jù)庫便成為可縮放共享數(shù)據(jù)庫。