INTRODUCTION
What will the SQL Sever database adminstrator's(DBA) jobs be like 10 years from now?

The is a broad qustion. It implies another question: will there be such a thing as a SQL Sever DBA in 10 years? By job tilte, I think the answer is clearly yes, there will certainly be SQL Sever DBAS in 2018. Much less clear, however, is what exactly SQL Sever DBAS will spend their time doing. This paper offer some answer to this question based on the current and foreseeable industry and technological trends.

<
介紹：
十年后SQL Sever數(shù)據(jù)庫管理員這個位置發(fā)展成什么樣子？

這是一個很大的問題，這也暗示這另一個問題的答案： 在十年后是否還會存在數(shù)據(jù)庫管理員這樣一個概念？ 看這個職位的頭銜答案是顯然的，在2018年當(dāng)然還會存在SQL Sever數(shù)據(jù)庫管理員。然而那時的DBAS會做些什么就不是那么明顯了。這份報告通過對當(dāng)前和可預(yù)期的工業(yè)和技術(shù)的發(fā)展為這一個問題提供了一些可能的答案。
>

HISTORY

To look 10 years ahead, it's helpful to look 10 years back in the past. An old aphorism goes something like: to know where you are going you must know where you have been. It holds true much of the time. And not only does it apply to IT in general, but it also apply to the SQL Sever world pariticularly well.

<
歷史：
回顧過去對展望未來是很有幫助的。有句古話說，要知道你要去哪里那你必須知道你走過的地方。這確實(shí)要花費(fèi)很多時間，不僅僅是大概回顧IT的概況，還需要特別好的了解這個SQL Sever的世界。
>

1998: SQL Sever Growing Pains

In 1988, I had been a SQL Sever DBA for 4 years, haveing started out with version 4.21a in 1994. By 98, we on underway on migrating from version 6.5 to the newly rewritten SQL Sever 7. In those days, the job of the DBAS was mostly about getting SQL Sever to work because we are in a transition phase from  considering SQL Sever as a departmental-only RDBMS to using it for enterprise-wide applications. There arme some growing pains. Some plans are too ambitious. And there were a few failures.

<
1998： SQL Sever的坎坷成長

1998年，我已經(jīng)做了四年的DBA，從94年起，最開始用得4.21a的版本。到了98年，我們正在從6.5升級到剛剛重寫的SQL Sever 7.0在那個時候DBA的工作主要是會SQL Sever工作，因為在那個時侯我們處在一個過渡期，在考慮是將SQL Sever作為一個僅部門上的關(guān)系數(shù)據(jù)庫還是作為企業(yè)范圍的共享的應(yīng)用。這中間有一些坎坷，有些計劃太大了，遺留了一些失敗的案例。
>

Also in 1998, expansion of server environments was well underway during the population explosion. New application? No problem, fire up another NT server. Virues? Only on PCs, not on NT. Worms? Never heard of them; SQL Slammer was still years in the future. About the only thing that really concerned us back then was Y2K<千年蟲> looming ahead<迫在眉睫>.

<
同樣是在1998年，人口的劇增導(dǎo)致的服務(wù)要求的擴(kuò)大。新的技術(shù)？沒有問題，再啟動一個NT Sever。病毒？在pc機(jī)上而已，不是在服務(wù)器上。蠕蟲？從來沒聽說過；SQL末路還在遙遠(yuǎn)的未來。而在那個時候唯一迫在眉睫要我們關(guān)注的是千年蟲事件。
>

2008: A Host of Broade Issues

Times have changed to be sure. Issues that were not even on our radar screens back in 1998 are at the forefront today. Issues that of paramount<最重要的，最高的> importance back then have disappeared. The question of whether SQL Sever will work for a given application is now moot. We know it will.

<
當(dāng)然時代已經(jīng)改變。98年出現(xiàn)在雷達(dá)屏幕上的問題現(xiàn)在就在眼前。那時相當(dāng)嚴(yán)峻的問題已經(jīng)不在了。關(guān)于SQL Sever是否能夠為給定的應(yīng)用程序工作的討論已經(jīng)沒有意義了，我們知道它會的。
>

Today's issues are much broader and there are more of them. Security, for example, has become multi-faceted in recent years, with the following, equally important issues:
1.Protection from viruses,worms,denial-of-service attacks
2.Protection of data
3.Audition of data
4.Disposal of data
Compliance requirements, such as Sarbanes-Oxley, while closely related to security, goes much deeper and can have major implications for database resourse utilization. In some companies, e-discovery has eclipsed Sarbanes-Oxley as the biggest non-productive resource consumer.

<
如今的問題更多更廣。比如說安全，近年來已演變?yōu)槎鄬用娴模ㄒ韵聨讉€重要的部分：
1.防病毒，蠕蟲，和拒絕服務(wù)攻擊
2.數(shù)據(jù)保護(hù)
3.數(shù)據(jù)審核
4.數(shù)據(jù)處理
企業(yè)合格要求走的越來越深，要求了對數(shù)據(jù)庫資源的利用，像同安全緊密相聯(lián)系的薩班斯-奧克斯法案。在有些公司，e-discovery解決法案已經(jīng)超越了薩班斯法案的應(yīng)用，成為了最大的非生產(chǎn)性的資源消費(fèi)。
>

The data growth explosion continues at an accelarated pace. SQL Sever DBAs find it more dificult to get their databases backed up<備份>. Fortunately, there are tools such as Quest Software's LiteSpeed that can shrink database backup files to a fraction<小部分，分?jǐn)?shù)> of their normal size.

<
數(shù)據(jù)爆發(fā)仍然在以加速度增長，SQL Sever DBAs發(fā)現(xiàn)數(shù)據(jù)庫數(shù)據(jù)備份越來越難。幸運(yùn)的事，現(xiàn)在有工具可以將數(shù)據(jù)庫備份文件壓縮到其正常大小的一小部分，比如Quest Software的LiteSpeed。“搞了半天原來是在做廣告”
>

Will the crucial issues we face today disappear in 2008? It's possible. It's not that audition, viruses, and scurity won't matter. It's that the way we handle those things will have become so mundance<普通，平凡> that we will no longer spend much time thinking about them. A standard SQL deployment<部署> will imply that all data is encrpted, changes are logged<記錄日志>, patching is automatic and unattended.

<
2018:新的一系列問題

我們現(xiàn)在的面臨的關(guān)鍵問題在2018年將會消失么？有這種可能。但不是審核，病毒，和安全問題就不再存在，而是我們處理這些問題的方式太熟悉普通而不用花費(fèi)太多時間。一個標(biāo)準(zhǔn)的SQL Sever部署需要數(shù)據(jù)加密，日志修改，自動和隱蔽修補(bǔ)。
>

Instead of these compliance and security issues, we have a new batch of problems to deal with. The rest of this paper explores some of the industry and technological trends that are either alread occuring or that are expected to occur in the next 10 years. We will explore what those trends will mean for the SQL Server DBA.
<
沒有了這些安全和規(guī)程的問題，又有新的問題需要我們處理。下面報告要探索一下產(chǎn)業(yè)技術(shù)趨勢，這其中有些已經(jīng)出現(xiàn)，有些在未來十年將會產(chǎn)生。我們來探求這些趨勢對SQL Sever數(shù)據(jù)庫管理員意味著什么。
>

TECHNOLOGICAL TRENDS
Hints<線索，淺析> in SQL 2008

SQL Server 2008 provide new features that provide some insight into the direction of database administration in the coming years. The new Declarative Management Framework (DMF) for example-which is basically a means to define policies and apply them across the enterprise on multiple instances-is a step away from individual instance management.
<
淺析SQL 2008
SQL Server 2008 提供了一些新特性暗示了DBA的在未來幾年的方向。比如基于策略化管理的Declarative Management Framework（DMF），將被應(yīng)用與公司的多實(shí)例環(huán)境，與單實(shí)例管理僅有一步之遙。
>

Third-party<承擔(dān)第三方責(zé)任> venders<零售商> have alread started down the path. For example, Quest Software's latest version of Change Director provides robust<強(qiáng)大的> fuctionality<功能> to manage an entire enterprise's SQL Agent jobs from a single point. More and more, tools and functionality will be geared<n工具，v使適合> towards managing the SQL Sever farms rather than the individual instances.
<
第三方廠家已經(jīng)開始采用這種策略。比如Quest Software的Change Director的新版本提供了強(qiáng)大的功能來實(shí)現(xiàn)從一個點(diǎn)上來管理整個公司的SQL代理工作。越來越多的工具和功能在試圖實(shí)現(xiàn)場服務(wù)器模式，而非獨(dú)立服務(wù)器模式。
>

Another new SQL 2008 feature is the Recource Governor<資源管理>. This much-needed feature allow the DBAs to set priorities and resource limits on individual jobs, which is a key in preventing processes from getting starved for resources. Yet another is new feature is the "Hot Add Cpu" that will allow the addition of CPUs to supported hardware without downtime.
<
另一個SQL 2008新特性是資源管理，這個常用的特性允許管理員為個體工作設(shè)置優(yōu)先級和資源限制。這有效的防止了因資源處于餓死的進(jìn)程。還有一個特性是“Hot-Add-CPU”，它允許在不停機(jī)的狀況下為硬件添加可兼容的cpu。
>

These new features point to a future in which SQL Severs are managed at the enterprise-level with dynamic resource allocation<動態(tài)資源分配>.As this trend continues, the SQL Sever DBA's job will evolve with the changing landscape.
<這些新特性指出了SQL在企業(yè)級上動態(tài)資源分配的前景，按此趨勢發(fā)展，SQL Sever管理員的工作同樣要隨著發(fā)展改變>

參考資料：

1.“千年蟲”問題的根源始于60年代。當(dāng)時計算機(jī)存儲器的成本很高，如果用四位數(shù)字表示年 份，就要多占用存儲器空間，就會使成本增加，因此為了節(jié)省存儲空間，計算機(jī)系統(tǒng)的編程 人員采用兩位數(shù)字表示年份。隨著計算機(jī)技術(shù)的迅猛發(fā)展，雖然后來存儲器的價格降低了， 但在計算機(jī)系統(tǒng)中使用兩位數(shù)字來表示年份的做法卻由于思維上的慣性勢力而被沿襲下來， 年復(fù)一年，直到新世紀(jì)即將來臨之際，大家才突然意識到用兩位數(shù)字表示年份將無法正確辨 識公元2000年及其以后的年份。1997年，信息界開始拉起了“千年蟲”警鐘，并很快引起了 全球關(guān)注。


2.上世紀(jì)末本世紀(jì)初，各種公司丑聞屢屢出現(xiàn)，導(dǎo)致美國國會出臺了《2002 年薩班斯-奧克斯利法案》（the Sarbanes-Oxley Act of 2002，簡稱SOX法案）。它對公司治理有著極為嚴(yán)格和苛刻的要求，它要求公司針對產(chǎn)生財務(wù)交易的所有作業(yè)流程，都做到能見度、透明度、控制、通訊、風(fēng)險管理和欺詐防范，且這些流程必須詳加記錄到可追查交易源頭的地步。SOX法案的要求是全面且復(fù)雜的。SOX法案對于上市公司來說，是一個嚴(yán)峻的挑戰(zhàn)，同時也是一個改善公司治理的機(jī)會。

3.Compliance Requirement

4.e-discovery 解決方案

5.Windows SharePoint Services Configurations配置模式
You can choose between two configurations for Windows SharePoint Services: stand-alone server or server farm. If you anticipate only light usage of your Web sites, you can use the stand-alone server configuration. If you are supporting Web sites in a large organization or as an Internet service provider (ISP), and anticipate heavy usage and a lot of data, you will most likely want to use the server farm configuration.WSS2支持兩種配置模式：獨(dú)立服務(wù)器模式和場服務(wù)器模式。