sql server 2000 中的“復(fù)制數(shù)據(jù)庫向?qū)А盵外文翻譯].rar
sql server 2000 中的“復(fù)制數(shù)據(jù)庫向?qū)А盵外文翻譯],sql server 2000 中的“復(fù)制數(shù)據(jù)庫向?qū)А盵外文翻譯]包含中文翻譯和英文原文，內(nèi)容詳細(xì)完整，建議下載參考！中文： 4070 字英文： 15500字符 復(fù)制數(shù)據(jù)庫向?qū)?sql server 2000 中的新實(shí)用工具，供您從 sql server 7.0 或 sql server 2000 向 sql ser...
該文檔為壓縮文件,包含的文件列表如下:
內(nèi)容介紹
原文檔由會員 xiaowei 發(fā)布
SQL Server 2000 中的“復(fù)制數(shù)據(jù)庫向?qū)А盵外文翻譯]
包含中文翻譯和英文原文，內(nèi)容詳細(xì)完整，建議下載參考！
中文： 4070 字
英文： 15500字符
復(fù)制數(shù)據(jù)庫向?qū)?SQL Server 2000 中的新實(shí)用工具，供您從 SQL Server 7.0 或 SQL Server 2000 向 SQL Server 2000 移動或復(fù)制數(shù)據(jù)庫。該復(fù)制或移動過程相當(dāng)簡便，看起來對工作幾乎沒有任何影響。本文提供有關(guān)“復(fù)制數(shù)據(jù)庫向?qū)А边\(yùn)行方式的信息，同時(shí)概要說明在使用該向?qū)r(shí)需要注意的一些問題。
“復(fù)制數(shù)據(jù)庫向?qū)А钡倪\(yùn)行方式
打開“復(fù)制數(shù)據(jù)庫向?qū)А保?• 在“SQL Server 企業(yè)管理器”中，單擊管理，然后單擊運(yùn)行向?qū)А?
• 右鍵單擊數(shù)據(jù)庫文件夾，單擊所有任務(wù)，然后單擊復(fù)制數(shù)據(jù)庫向?qū)?..-
• 在命令提示符下，鍵入 Cdw.exe，然后按 Enter 鍵。
該向?qū)Х蛛x要復(fù)制或移動的數(shù)據(jù)庫，將與該數(shù)據(jù)庫相關(guān)的文件復(fù)制到目標(biāo)服務(wù)器，然后再附加該數(shù)據(jù)庫。數(shù)據(jù)庫的分離和附加是通過以下存儲過程執(zhí)行的： • sp_detach_db
有關(guān)這些存儲過程的更多信息，請參閱“SQL Server 聯(lián)機(jī)叢書”中的“sp_attach_db”和“sp_detach_db”主題 ......
UPDATING AN EXISTING SQL SERVER APP CALLS FOR RESOURCEFUL ACTION
I've just inherited a project that was created by a group of employees who are no longer with my company. It's a Microsoft SQL Server database and Active Server Pages [ASP] application that deals with order tracking, inventory, and customer service. For the most part it works fine, so there hasn't been much need to touch it. However, we now need to add customer address and credit card data so repeat visitors don't have to keep entering the same data. I'm new to Active Server Pages and SQL Server, but they look easy enough. I've encountered a few problems: On the middle tier, if I make changes to the global.asa file, it kicks everyone out of the application and sometimes crashes Internet Information Server. Is there any graceful way to manage global.asa?
My second problem is on the database side. When a user deletes a shipping address, I need to delete all the names that have been shipped to that address. I've created a delete trigger, but it's not working.
Finally, I'm really confused about ADO vs. OLE DB vs. ODBC vs. the million other acronyms involved in data access. What should I be using?
B. Segel
Brooks: I think you have more questions here than we can answer. So the first step is to find yourself some good resources for ASP/SQL Server. I recommend www.15seconds.com,www.4guysfromrolla.com, and their various newsgroups.
The quick answer to your first question regarding global.asa is "no." The best way I know to manage global.asa changes works only on a server farm load-balanced by something such as a Cisco Local Director or Alteon AceSwitch. What I do in that case is take one or more servers out of service for a while until their session count drifts down to zero. Then, I update the global.asa file on those servers and put them in service while taking the other servers out of service. Voila. New visitors will get the new global.asa, old users get the old one, and the transition is smooth. That is, unless your global.asa change reflects a major change in the back end or elsewhere that doesn't allow both versions to be in use at once. In that case, you're in trouble ......
包含中文翻譯和英文原文，內(nèi)容詳細(xì)完整，建議下載參考！
中文： 4070 字
英文： 15500字符
復(fù)制數(shù)據(jù)庫向?qū)?SQL Server 2000 中的新實(shí)用工具，供您從 SQL Server 7.0 或 SQL Server 2000 向 SQL Server 2000 移動或復(fù)制數(shù)據(jù)庫。該復(fù)制或移動過程相當(dāng)簡便，看起來對工作幾乎沒有任何影響。本文提供有關(guān)“復(fù)制數(shù)據(jù)庫向?qū)А边\(yùn)行方式的信息，同時(shí)概要說明在使用該向?qū)r(shí)需要注意的一些問題。
“復(fù)制數(shù)據(jù)庫向?qū)А钡倪\(yùn)行方式
打開“復(fù)制數(shù)據(jù)庫向?qū)А保?• 在“SQL Server 企業(yè)管理器”中，單擊管理，然后單擊運(yùn)行向?qū)А?
• 右鍵單擊數(shù)據(jù)庫文件夾，單擊所有任務(wù)，然后單擊復(fù)制數(shù)據(jù)庫向?qū)?..-
• 在命令提示符下，鍵入 Cdw.exe，然后按 Enter 鍵。
該向?qū)Х蛛x要復(fù)制或移動的數(shù)據(jù)庫，將與該數(shù)據(jù)庫相關(guān)的文件復(fù)制到目標(biāo)服務(wù)器，然后再附加該數(shù)據(jù)庫。數(shù)據(jù)庫的分離和附加是通過以下存儲過程執(zhí)行的： • sp_detach_db
有關(guān)這些存儲過程的更多信息，請參閱“SQL Server 聯(lián)機(jī)叢書”中的“sp_attach_db”和“sp_detach_db”主題 ......
UPDATING AN EXISTING SQL SERVER APP CALLS FOR RESOURCEFUL ACTION
I've just inherited a project that was created by a group of employees who are no longer with my company. It's a Microsoft SQL Server database and Active Server Pages [ASP] application that deals with order tracking, inventory, and customer service. For the most part it works fine, so there hasn't been much need to touch it. However, we now need to add customer address and credit card data so repeat visitors don't have to keep entering the same data. I'm new to Active Server Pages and SQL Server, but they look easy enough. I've encountered a few problems: On the middle tier, if I make changes to the global.asa file, it kicks everyone out of the application and sometimes crashes Internet Information Server. Is there any graceful way to manage global.asa?
My second problem is on the database side. When a user deletes a shipping address, I need to delete all the names that have been shipped to that address. I've created a delete trigger, but it's not working.
Finally, I'm really confused about ADO vs. OLE DB vs. ODBC vs. the million other acronyms involved in data access. What should I be using?
B. Segel
Brooks: I think you have more questions here than we can answer. So the first step is to find yourself some good resources for ASP/SQL Server. I recommend www.15seconds.com,www.4guysfromrolla.com, and their various newsgroups.
The quick answer to your first question regarding global.asa is "no." The best way I know to manage global.asa changes works only on a server farm load-balanced by something such as a Cisco Local Director or Alteon AceSwitch. What I do in that case is take one or more servers out of service for a while until their session count drifts down to zero. Then, I update the global.asa file on those servers and put them in service while taking the other servers out of service. Voila. New visitors will get the new global.asa, old users get the old one, and the transition is smooth. That is, unless your global.asa change reflects a major change in the back end or elsewhere that doesn't allow both versions to be in use at once. In that case, you're in trouble ......
