¢éÍ¡Ó˹´ÃкºÂèÍ¢ͧ i/o ¢Í§à«ÔÃì¿àÇÍÃì SQL ¢Í§ Microsoft ÊÓËÃѺ°Ò¹¢éÍÁÙÅ tempdb

Microsoft SQL Server µéͧãªéÃкºÂèÍ I/O ·Õèãªéà¡çº°Ò¹¢éÍÁÙŢͧÃкºáÅмÙéãªéÍÂèÒ§ÊÁºÙóì honor ¤ÇÒÁµéͧ¡ÒÃà¢Õ¹Åèǧ˹éÒÅçÍ¡ (WAL) ¼èÒ¹ÃÑ¡ÉÒ I/O ੾ÒÐ ¢éÍ¡Ó˹´àËÅèÒ¹ÕéäÁè¨Óà»ç¹µéͧ honor ¤Ø³ÊÁºÑµÔ ACID ¢Í§¸ØáÃÃÁ: Atomic, Consistent, Isolated áÅÐ Durable ÃÒÂÅÐàÍÕ´à¡ÕèÂǡѺ¤ÇÒÁµéͧ¡ÒäÇÒÁÊÍ´¤Åéͧ¢Í§ÃкºÂèÍ I/O ¨ÐÁÕ¡ÒÃÍéÒ§ÍÔ§µèÍ仹Õé:

• ¢Ñé¹¾×é¹°Ò¹¢Í§ I/O 2000 à«ÔÃì¿àÇÍÃì sql
  http://technet.microsoft.com/en-us/library/cc966500.aspx

  (http://technet.microsoft.com/en-us/library/cc966500.aspx)
  ËÁÒÂà˵Ø:¹Í¡¨Ò¡¹Õ麷¤ÇÒÁ¹Õéãªé¡Ñº SQL Server 2005
• ¡Ò÷Ӻѹ·Ö¡¢Í§ sql Server 7.0 áÅÐ SQL Server 2000 áÅÐ algorithms ¡ÒÃà¡çº¢éÍÁÙÅ¢ÂÒ¤ÇÒÁ¹èÒàª×èͶ×ͧ͢¢éÍÁÙÅ
  http://support.microsoft.com/default.aspx?scid=kb;en-us;230785

  (http://support.microsoft.com/default.aspx?scid=kb;en-us;230785)

ÃÒ¡ÒõèÍ仹Õéà»ç¹º·ÊÃØ»¢Í§¤ÇÒÁµéͧ¡ÒÃÍÂèÒ§ÃÇ´àÃçÇ:

• ¡ÒÃà¢Õ¹¡ÒÃÊÑ觫×é͵éͧ¶Ù¡ÃÑ¡ÉÒäÇé
• ¤ÇÒÁÊÍ´¤Åéͧ㹡ÒÃà¢Õ¹·ÕèÍéÒ§¶Ö§µéͧÁÕ¡ÒÃà¡çºÃÑ¡ÉÒ
• µéͧà»ç¹»ÅÍ´ÀÑÂà¢Õ¹àÊÁÍ ã¹/º¹Ê×èÍ·ÕèàʶÕÂÃ
• »éͧ¡Ñ¹ I/O torn µéͧà¡Ô´¢Öé¹

¡ÒúÓÃاÃÑ¡ÉÒ durability ÊӤѭÊÓËÃѺ°Ò¹¢éÍÁÙÅÍ×è¹ æ ·Ñé§ËÁ´Âѧ¤§ÍÂÙè áµèÍÒ¨ relaxed ÊÓËÃѺ¡ÒÃtempdbdatabase. µÒÃÒ§µèÍä» summarizes ËÅÒÂ æ ¢Í§¤ÇÒÁµéͧ¡Òâͧ I/O ·ÕèÊӤѭÊÓËÃѺ°Ò¹¢éÍÁÙÅ SQL Server* à«¡àµÍÃì¢Í§·Ãҹ᫤ªÑ¹ rewrites à¡ÕèÂÇ¢éͧ¡Ñº¡ÒôÓà¹Ô¹¡Ò÷ÕèÅçÍ¡äÇé·Ñé§ËÁ´ â´ÂÃкºÂèÍ¡ÒÃ͹حҵãËéÁÕà«¡àµÍÃì·Ñé§ËÁ´ÂéÒ ᷹ ËÃ×Í¡àÅÔ¡ä»ÂѧÃÙ»ÀÒ¾µé¹©ºÑº â´Â»¡µÔ¨Ð discouraged rewrites àËÅèÒ¹Õéà¹×èͧ¨Ò¡¡Ò÷ÕèàµÔÁ overhead µéͧ´Óà¹Ô¹¡ÒÃàªè¹ µÑÇÍÂèÒ§¹Õé¨Ðà»ç¹â»Ãá¡ÃÁÍÃö»ÃÐ⪹ì¢Í§¡ÒèѴàÃÕ§¢éÍÁÙÅ·ÕèÁÕ¡ÒÃÂéÒ¢éÍÁÙÅá¿éÁ äÁèÊÒÁÒö¶Ù¡á·¹·Õè ´éÇ·ÕèµÑé§ãËÁè¢Í§à«¡àµÍÃìà«¡àµÍÃìà´ÔÁã¹á¿éÁ¨¹¡ÇèÒà«¡àµÍÃìãËÁèáÅТéÍÁÙÅä´éÍÂèÒ§ÊÁºÙóì»ÅÍ´ÀÑ ·Õè remapping à«¡àµÍÃìµéͧà¡Ô´ã¹ÅѡɳзÕè¢Í§·Ãҹ᫤ªÑ¹·Õèà»ç¹ÊÒà˵آͧ¤ÇÒÁÅéÁàËÅÇã´ æ ÃÇÁ·Ñ駻ѭËÒ´éÒ¹¾Åѧ§Ò¹ re-establishment ¢Í§¢éÍÁÙŵ鹩ºÑº µÃǨÊͺãËéá¹èã¨ÇèÒ ¤Ø³ÁÕÅçÍ¡¡Å䡾ÃéÍÁãªé§Ò¹ã¹ÃÐËÇèÒ§¡Ãкǹ¡Òûéͧ¡Ñ¹¡ÒÃà¢éÒ¶Ö§¢éÍÁÙÅ·ÕèäÁè¶Ù¡µéͧ ª¹Ô´¹Õ駺 upholding tenants Í×è¹ æ ¢Í§ SQL Server I/O

survival ¢éÒÁ´Ñº

¡Ãкǹ¡ÒÃtempdb°Ò¹¢éÍÁÙÅà»ç¹¾×é¹·Õè·Õè scratch ÊÓËÃѺ SQL Server áÅÐ rebuilt àÁ×èÍàÃÔèÁµé¹·Ø¡ SQL Server ¡ÒÃàµÃÕÂÁãªé§Ò¹·Õèá·¹¤ÇÒÁµéͧ¡ÒâéÍÁÙÅä»Âѧ survive ¡ÒÃàÃÔèÁÃкº¤ÍÁ¾ÔÇàµÍÃìãËÁè

¡ÒôÓà¹Ô¹¡Òà rewrite à«¡àµÍÃì¢Í§·Ãҹ᫤ªÑ¹

à¾×èÍÃѺ»ÃСѹ¤ÇÒÁÊÓàÃ稢ͧ¡Ãкǹ¡ÒáÙé¤×¹ àªè¹¡ÒáÙé¤×¹Âé͹¡ÅѺáÅФÇÒÁÅéÁàËÅÇ ÃÐàºÕ¹á¿éÁºÑ¹·Ö¡µéͧ¶Ù¡à¡çºÍÂèÒ§¶Ù¡µéͧÍÂÙ躹Ê×èÍ·ÕèàʶÕÂáè͹·Õè˹éÒ¢éÍÁÙŶ١à¡çºäÇé áÅÐäÁèÊÒÁÒö¶Ù¡ rewritten â´ÂäÁèµéͧ honoring ¤Ø³ÊÁºÑµÔ¢Í§·Ãҹ᫤ªÑ¹ µéͧãªéÃкºÂèÍÂáÅÐ SQL Server à¾×èÍÃÑ¡ÉÒáÍ··ÃÔºÔǵì੾ÒÐ àªè¹¡ÒÃà¢Õ¹ÊÑè§ à«¡àµÍÃì¨Ñ´µÓáË¹è§ áÅТ¹Ò´à¢Õ¹ áÅÐÍ×è¹ æ àªè¹ I/O »ÅÍ´ÀѤسÅѡɳРoutlined ã¹àÍ¡ÊÒáÅèÒǶ֧¡è͹˹éÒ¹Õé ÊÓËÃѺ¡ÒÃtempdb°Ò¹¢éÍÁÙÅ ¡ÒáÙé¤×¹¢éÍÁÙŤÇÒÁÅéÁàËÅǨÐäÁè¨Óà»ç¹à¹×èͧ¨Ò¡°Ò¹¢éÍÁÙŶ١àµÃÕÂÁãªé§Ò¹ã¹ÃÐËÇèÒ§¡ÒÃàÃÔèÁµé¹¢Í§ SQL Server àÊÁÍ ÍÂèÒ§äáçµÒÁ ã¹tempdb°Ò¹¢éÍÁÙÅÂѧ¤§µéͧ¡ÒäÇÒÁÊÒÁÒö㹡ÒÃÂé͹¡ÅѺ ´Ñ§¹Ñé¹ ¤Ø³ÅѡɳкҧÍÂèÒ§¢Í§â¾Ãâ·¤ÍÅ WAL ÊÒÁÒö¶Ù¡ relaxed

ʶҹ·Õèà¡çºÊÓËÃѺtempdb°Ò¹¢éÍÁÙŵéͧ·Ó˹éÒ·Õè㹡Òà accordance ·Õèà¢éÁ§Ç´¡Ñºâ¾Ãâ·¤ÍÅ´ÔÊ¡ìä´Ã¿ì·ÕèÊÃéÒ§äÇéáÅéÇ ÇÔ¸Õ¡Ò÷Ñé§ËÁ´ ÍØ»¡Ã³ì·Õè¨Ðtempdbà¡çº°Ò¹¢éÍÁÙŵéͧ»ÃÒ¡¯¢Öé¹ áÅзÓ˹éÒ·Õèà»ç¹´ÔÊ¡ì·Ò§¡ÒÂÀÒ¾ãËéÍèÒ¹áÅéÇËÅѧ¨Ò¡¤ÇÒÁÊÒÁÒö㹡ÒÃà¢Õ¹ ¸ØáÃÃÁ¡ÒôÓà¹Ô¹§Ò¹ rewrite à«¡àµÍÃìÍÒ¨ÁÕ¤ÇÒÁµéͧ¡ÒÃà¾ÔèÁàµÔÁ¢Í§ implementations ੾ÒÐ µÑÇÍÂèÒ§àªè¹ µÒÁ SQL Server äÁèʹѺʹع°Ò¹¢éÍÁÙÅ·Õè»ÃѺà»ÅÕè¹ â´Âãªé¡ÒúպÍÑ´Ãкºá¿éÁ NTFS ä´éà¹×èͧ¨Ò¡¡ÒúպÍÑ´ NTFS ÊÒÁÒöà¢Õ¹ૡàµÍÃì¢Í§á¿éÁºÑ¹·Ö¡·ÕèÁÕÍÂÙèáÅéÇ¡ÒÃà¢Õ¹ áÅж×ÍÇèÒ hardened ¤ÇÒÁÅéÁàËÅÇã¹ÃÐËÇèÒ§¡Òà rewrite ª¹Ô´¹ÕéÍÒ¨·ÓãËé°Ò¹¢éÍÁÙÅ·Õè¨ÐãªéäÁèä´é àÊÕÂËÒ¢ͧ¢éÍÁÙÅÇèÒ SQL Server áÅéǶ×ÍÇèÒÁÕ¤ÇÒÁ»ÅÍ´ÀÑÂ

ËÁÒÂà˵Ø:sql Server 2005 ·Õè¢ÂÒ¡ÒúպÍÑ´à¾×èÍÍèÒ¹à¾Õ§°Ò¹¢éÍÁÙÅáÅСÅØèÁá¿éÁËÃ×Í¡ÒÃʹѺʹع See the SQL Server 2005 Books Online for complete details.

Transactional sector rewrite operations are pertinent to all SQL Server databases that include thetempdbdatabase. A growing variety of extended storage technologies use devices and utilities that can rewrite data that SQL Server considers secure. For example, some of the emerging technologies perform in-memory caching or data compression. In order to avoid severe database damage, any sector rewrite must have full transactional support in such a way that if a failure occurs, the data is rolled back to the previous sector images. This guarantees that SQL Server is never exposed to an unexpected interruption or data damage condition.

You may be able to put thetempdbdatabase on specialty subsystems, such as RAM disks, solid state, or other high speed implementations that cannot be used for other databases. However, the key factors presented in the “More Information” section must be considered when you evaluate these options.

Several factors should be carefully studied when you evaluate the storage location of thetempdbdatabase. µÑÇÍÂèÒ§àªè¹ ¡ÒÃtempdbdatabase usage involves, but is not limited to, memory footprint, query plan, and I/O decisions. The appropriate tuning and implementation of thetempdbdatabase can improve the scalability and responsiveness of a system. This section discusses the key factors in determining the storage needs for thetempdbdatabase.

High speed subsystems

There are various high speed subsystem implementations available on the market that provide SQL Server I/O subsystem protocol requirements but that do not provide durability of the media.

ÊÔè§ÊӤѭAlways confirm with the product vendor to guarantee full compliance with SQL Server I/O needs.

A RAM disk is one common example of such an implementation. RAM disks install the necessary drivers and enable part of the main RAM disk to appear as and function like any disk drive that is attached to the system. All I/O subsystems should provide full compliance with the SQL Server I/O requirements. However, it is obvious that a RAM disk is not durable media. Therefore, an implementation such as a RAM disk may only be used as the location of thetempdbdatabase and cannot be used for any other database.

Keys to consider before implementation and deployment

There are various points to consider before deployment of thetempdbdatabase on this kind of subsystem. This section uses a RAM disk as the basis for discussion, but similar outcomes occur in other high speed implementations.

I/O safety

Compliance of read after write and transactional sector writes is a must. Never deploy SQL Server on any system that does not fully support the SQL Server I/O requirements, or you risk damage and loss of your data.

Pages already cached (Double RAM cache)

Temporary tables are like all other tables in a database. They are cached by the buffer pool and handled by lazy write operations. Storing temporary table pages on a RAM disk causes double RAM caching, one in the buffer pool and one on the RAM disk. This directly takes away from the buffer pool’s total possible size and generally decreases the performance of SQL Server.

Giving up RAM

´ÔÊ¡ì RAM designates à»ç¹Êèǹ˹Ö觢ͧ RAM ËÅÑ¡ µÒÁª×èÍà·èÒ äÁèÁÕÍÂÙèËÅÒ implementations ¢Í§´ÔÊ¡ì·Õèãªé RAM áÅÐá¿éÁ·Õèãªé RAM caches ºÒ§ÍÂèÒ§ÂѧªèÇ I/O ¡ÒÂÀÒ¾·Õè´Óà¹Ô¹¡ÒÃÊÓÃͧ¢éÍÁÙŠͧ¤ì»ÃСͺËÅÑ¡¢Í§á¤ª¢Í§á¿éÁ·Õèãªé RAM ÁÕãËéâ´ÂµÃ§ãªéÍÍ¡¨Ò¡Ë¹èǤÇÒÁ¨Ó¡ÒÂÀÒ¾·Õèãªé â´Â SQL Server àÊÁÍÁÕËÅÑ¡°Ò¹·ÕèÃÑ´¡ØÁ·Õèà¾ÔèÁá¤á¿éÁ·Õèãªé RAM ªèÇÂà¾ÔèÁ»ÃÐÊÔ·¸ÔÀÒ¾¡Ò÷ӧҹ¢Í§á;ÅÔपѹ áÅÐäÁèÅ´»ÃÐÊÔ·¸ÔÀÒ¾¢Í§áººÊͺ¶ÒÁËÃ×Íâ»Ãá¡ÃÁ»ÃÐÂØ¡µìÍ×è¹

¡ÒûÃѺáµè§¡è͹

â»Ãá¡ÃÁ»ÃÐÂØ¡µì¤ÇûÃѺáµè§¡ÒÃàÍÒ hashes ·ÕèÍÒ¨¡èÍãËéà¡Ô´¡ÒÃãªéáÅСÒÃàÃÕ§ÅӴѺäÁè¨Óà»ç¹ áÅÐäÁèµéͧ¡ÒÃtempdbdatabase. ËÅÒ¤ÃÑé§à¾ÔèÁ´Ñª¹ÕÊÒÁÒöàÍÒ¤ÇÒÁµéͧ¡ÒÃàÃÕ§ÅӴѺ ËÃ×ÍáÎã¹á¼¹¹Ñé¹ä´éÍÂèÒ§ÊÁºÙóì àÅ¢¹Ó˹éÒà¾×èÍ»ÃÐÊÔ·¸ÔÀÒ¾·Õè´Õ·ÕèÊØ´â´ÂäÁè¨Óà»ç¹µéͧãªé¡ÒÃtempdbdatabase.

¨Ø´»ÃÐ⪹ì·Õèà»ç¹ä»ä´é

»ÃÐ⪹ì¢Í§¡ÒÃÂéÒÂtempdb°Ò¹¢éÍÁÙÅã¹Ãкº·ÕèÁÕ¤ÇÒÁàÃçÇÊÙ§ÊÒÁÒö¶Ù¡¡Ó˹´â´Â¼èÒ¹¡Ò÷´Êͺ rigorous áÅСÒûÃÐàÁÔ¹ workloads á;ÅÔपѹà·èÒ¹Ñé¹ »ÃÔÁÒ³·ÕèÁÕ¡Òö١ studied ÍÂèÒ§Ãͺ¤ÍºÊÓËÃѺÅѡɳзÕè¨Ðtempdb°Ò¹¢éÍÁÙÅÍÒ¨ä´éÃѺ»ÃÐ⪹ì¨Ò¡ áÅФÇÒÁ»ÅÍ´ÀÑ¢ͧ I/O µéͧä´éÃѺ¡ÒÃÂ×¹Âѹ¡è͹¡ÒûÃѺãªé

¡ÒôÓà¹Ô¹§Ò¹àÃÕ§ÅӴѺáÅÐáηӧҹÃèÇÁ¡ÑºµÑǨѴ¡ÒÃ˹èǤÇÒÁ¨Ó¢Í§ SQL Server à¾×èÍ¡Ó˹´¢¹Ò´¢Í§¾×é¹·Õè scratch ã¹Ë¹èǤÇÒÁ¨ÓÊÓËÃѺáµèÅСÒôÓà¹Ô¹¡ÒÃàÃÕ§ÅӴѺËÃ×ÍáΪ ·Ñ¹·Õ·Õè¢éÍÁÙÅàÃÕ§ÅӴѺËÃ×ÍáÎà¡Ô¹¾×é¹·Õè scratch ã¹Ë¹èǤÇÒÁ¨Ó»Ñ¹Êèǹ ÍÒ¨ÊÒÁÒöà¢Õ¹¢éÍÁÙÅä»Âѧtempdbdatabase. ÍÑÅ¡ÍÃÔ·ÖÁ¹Õéä´é¶Ù¡¢ÂÒÂã¹ SQL Server 2005 Å´tempdb°Ò¹¢éÍÁÙŤÇÒÁµéͧ¡ÒÃãªé§Ò¹º¹ SQL Server ÃØ蹡è͹˹éÒ¹Õé µÑÇÍÂèÒ§àªè¹ â´ÂàÃÕ§ºÑ§¤Ñº pure ¢Í§µÒÃÒ§·Õèãªé ´Ñª¹ÕäÁè ¨Ò¡ãºÊÑè§ áÅСÒáÓ˹´·ÕèàËÁ×͹¡Ñ¹ÎÒÃì´áÇÃì¤èÒ SQL Server 2005 áÊ´§»ÃѺ»Ãا noticeable º¹ SQL Server 2000 ËÃ×ÍäÁè

¢éͤÇÃÃÐÇѧÍ͡ẺÁÒà¾×èÍãªéºÑ­ªÕÊÓËÃѺÃдѺ¢Í§Ë¹èǤÇÒÁ¨ÓáÅСԨ¡ÃÃÁẺÊͺ¶ÒÁ»Ñ¨¨ØºÑ¹àÁ×èÍ·Ó¡ÒõѴÊÔ¹ã¨á¼¹áººÊͺ¶ÒÁ·Õèà¡ÕèÂÇ¢éͧ¡Ñº¡ÒÃãªé sql Servertempdb°Ò¹¢éÍÁÙÅ¡ÒôÓà¹Ô¹§Ò¹ ´Ñ§¹Ñé¹ ¡ÓäûÃÐÊÔ·¸ÔÀÒ¾à»ÅÕè¹ÁÒ¡¢Öé¹ workloads áÅСÒÃÍ͡Ẻá;¾ÅÔपѹ àÃÒ¢Íá¹Ð¹ÓãËé ¤Ø³·Ó¡Ò÷´Êͺ ´éÇÂâ«Å٪ѹ·Õèµéͧ¡ÒáÓ˹´¡Óä÷Õèà»ç¹ä»ä´é áÅлÃÐàÁÔ¹¤ÇÒÁµéͧ¡ÒäÇÒÁ»ÅÍ´ÀÑ¢ͧ I/O ¡è͹¡ÒûÃѺãªé¡ÒÃ

ãªé SQL Servertempdb°Ò¹¢éÍÁÙÅ¡ÒèѴ¡ÒáԨ¡ÃÃÁµèÒ§ æ ·Õèà¡ÕèÂÇ¢éͧ¡Ñº¡ÒÃàÃÕ§ÅӴѺ hashes ¡ÒèѴà¡çºÃØè¹á¶Ç áÅÐ temp µÒÃÒ§:

• µÒÃÒ§ªÑèǤÃÒǶ١ÃÑ¡ÉÒäÇé â´ÂµÒÁ»¡µÔ¾ÙºÑ¿à¿ÍÃì·Õ辺â´Â·ÑèÇä»ÊÓËÃѺྡྷéÍÁÙÅ áÅÐâ´Â·ÑèÇ仨ÐäÁèÁÕ»ÃÐ⪹ì»ÃÐÊÔ·¸ÔÀÒ¾¨Ò¡ implementations ÃкºÂè;ÔàÈÉ
• ¡Ãкǹ¡ÒÃtempdbÁÕãªé°Ò¹¢éÍÁÙÅà»ç¹¾×é¹·Õè·Õè scratch hashes áÅÐàÃÕ§ÅӴѺ ¡ÒÃÅ´àÇÅÒὧ I/O ÊÓËÃѺ¡ÒôÓà¹Ô¹¡ÒÃàªè¹ÍÒ¨ beneficial ÍÂèÒ§äáçµÒÁ ·ÃÒº·Õèà¾ÔèÁ´Ñª¹Õà¾×èÍËÅÕ¡àÅÕ觡ÒÃáÎ ËÃ×ÍàÃÕ§ÅӴѺÍÒ¨·ÓãËéà¡Ô´¡ÒÃàÃÕ¡ãªé»ÃÐ⪹ì·Õè¤ÅéÒ¡ѹ

Ãѹ baselines ´éÇ áÅÐâ´ÂäÁèµéͧ¡ÒÃtempdb°Ò¹¢éÍÁÙÅ·Õèà¡çºÍÂÙèã¹ÃкºÂèÍ¢ͧ¤ÇÒÁàÃçÇÊÙ§à¾×èÍà»ÃÕºà·Õº¼Å»ÃÐ⪹ì Êèǹ¢Í§¡Ò÷´Êͺ¤ÇÃÃÇÁ¡ÒÃÊͺ¶ÒÁ¡Ñº°Ò¹¢éÍÁÙŢͧ¼Ùéãªé·ÕèäÁèà¡ÕèÂÇ¢éͧ¡Ñº¡ÒÃàÃÕ§ÅӴѺ hashes ËÃ×͵ÒÃÒ§ªÑèǤÃÒÇ áÅÐÂ×¹ÂѹÇèÒ áººÊͺ¶ÒÁàËÅèÒ¹ÕéäÁèä´éÃѺÁÒ¡¨Ò¡ àÁ×èͤس»ÃÐàÁÔ¹Ãкº µÑǺ觪Õé»ÃÐÊÔ·¸ÔÀÒ¾¡Ò÷ӧҹµèÍ仹ÕéÊÒÁÒöÁÕ»ÃÐ⪹ì

Transactional sector rewrite example

The following example elaborates the data security that is required by SQL Server databases.

Assume a RAM disk vendor uses an in-memory compression implementation. The implementation must be correctly encapsulated by providing the physical appearance of the file stream as if the sector was aligned and sized so SQL Server is unaware and correctly secured from the underlying implementation. Look at the compression example closer.The device may perform the following actions to help secure sector 1’s data when it is combined with sector 2’s data.The ability to provide locking mechanisms around the sector modifications and roll back the changes when the sector exchange attempt fails is considered transitionally compliant. For implementations that use physical storage for extended backing, it would include the appropriate transaction log aspects to help secure and roll back changes that were applied to the on-disk structures to maintain the integrity of the SQL Server database files.

Any device that enables the rewrite of sectors must support the rewrites in a transactional way so that SQL Server is not exposed to data loss.

ËÁÒÂà˵Ø:The instance of SQL Server is restarted when online I/O and rollback failures occur in thetempdbdatabase.

Be careful when you move thetempdbdatabase.

Be careful when you move thetempdbdatabase because if thetempdbdatabase cannot be created, SQL Server will not start. ¶éÒ¡ÒÃtempdbdatabase cannot be created, start SQL Server by using the (-f) startup parameter and move thetempdbdatabase to a valid location.

To change the physical location of thetempdb°Ò¹¢éÍÁÙÅ ¡Ò÷ӵÒÁ¢Ñ鹵͹àËÅèÒ¹Õé:

1. Use the ALTER DATABASE statement and the MODIFY FILE clause to change the physical file names of each file in thetempdbdatabase to refer to the new physical location, such as the new disk.

   Alter database tempdb modify file 
   (name = tempdev, filename = 'C:\MyPath\tempdb.mdf')
   
   Alter database tempdb modify file 
   (name = templog, filename = 'C:\MyPath\templog.ldf')

2. Stop and then restart SQL Server.

Partner product certifications are not a guaranty of compatibility or safety

A third-party product or a particular vendor can receive a Microsoft logo certification. However, partner certification or a specific Microsoft logo does not certify compatibility or fitness for a particular purpose in SQL Server.

¡ÒÃʹѺʹع

If you use a subsystem with SQL Server that supports the I/O guarantees for transactional database use as described in this article, Microsoft will provide support for SQL Server and SQL Server-based applications. However, issues with, or caused by, the subsystem will be referred to the manufacturer.

ÊÓËÃѺtempdb»Ñ­ËÒ·Õèà¡ÕèÂǡѺ°Ò¹¢éÍÁÙÅ ºÃÔ¡ÒÃʹѺʹع¢Í§ Microsoft ¨Ð¢ÍãËé¤Ø³ÊÒÁÒöÂéÒÂtempdbdatabase. µÔ´µèͼÙé¨Ó˹èÒÂÍØ»¡Ã³ì¢Í§¤Ø³à¾×è͵ÃǨÊͺÇèÒ ¤Ø³ä´éÍÂèÒ§¶Ù¡µéͧ»ÃѺãªé áÅСÓ˹´¤èÒÍØ»¡Ã³ìÊÓËÃѺ¡ÒÃãªé°Ò¹¢éÍÁÙŢͧ·Ãҹ᫤ªÑ¹

Microsoft äÁèÃѺÃͧ ËÃ×͵ÃǨÊͺ¡Ò÷ÓãËé¼ÅÔµÀѳ±ìÍ×è¹ æ §Ò¹ÍÂèÒ§¶Ù¡µéͧ¡Ñº SQL Server ¹Í¡¨Ò¡¹Õé Microsoft äÁèãËéÁÕ¡ÒÃÃѺ»ÃСѹ guaranty ËÃ×ͤÓÊÑ觢ͧ¤ÇÒÁàËÁÒÐÊÁ¢Í§¼ÅÔµÀѳ±ì¢Í§ºÃÔÉÑ·Í×è¹ã´ æ ÊÓËÃѺãªé¡Ñº SQL Server

ËÒ¡µéͧ¡Ò÷ÃÒº¢éÍÁÙÅà¾ÔèÁàµÔÁ â»Ã´¤ÅÔ¡·ÕèËÁÒÂàÅ¢º·¤ÇÒÁµèÍ仹Õéà¾×èÍ´Ùº·¤ÇÒÁã¹ Microsoft Knowledge Base::¢éÍÁÙÅã¹àÍ¡ÊÒùÕéáÊ´§ÁØÁÁͧ»Ñ¨¨ØºÑ¹¢Í§ Microsoft Corporation »Ñ­ËÒ¡ÅèÒǶ֧ ³Çѹ·Õè¢Í§¡ÒûÃСÒÈ à¹×èͧ¨Ò¡ Microsoft µéͧµÍºÊ¹Í§àÁ×è͵éͧ¡ÒÃà»ÅÕè¹à§×è͹䢡ÒõÅÒ´ Áѹ¨ÐäÁèÊÒÁÒöá»Å¼Åà»ç¹ Ẻ commitment part ¢Í§ Microsoft áÅÐ Microsoft äÁèÃѺ»ÃСѹ¤ÇÒÁ¶Ù¡µéͧ¢Í§¢éÍÁÙÅ·Õè¹Óàʹ͵èÍËÅѧ¨Ò¡Çѹ·Õè¢Í§¡ÒûÃСÒÈ

àÍ¡ÊÒ÷ҧ෤¹Ô¤¹Õé¨ÐãªéÊÓËÃѺ¡ÒÃãËé¢éÍÁÙÅà·èÒ¹Ñé¹ microsoft ·ÓãËéäÁèÃѺ»ÃСѹ express ·Ñé§â´Â¹Ñ ËÃ×Í statutory ¹Õé¶Ö§¢éÍÁÙÅã¹àÍ¡ÊÒùÕé

complying â´Â¡®ËÁÒÂÅÔ¢ÊÔ·¸Ôìà¡ÕèÂÇ¢éͧ·Ñé§ËÁ´à»ç¹¤ÇÒÁÃѺ¼Ô´ªÍº¢Í§¼Ùéãªé â´ÂäÁèÁÕ¡ÒèӡѴÊÔ·¸ÔìÀÒÂãµéÅÔ¢ÊÔ·¸Ôì äÁèÁÕÊèǹ¢Í§àÍ¡ÊÒùÕéÍÒ¨¶Ù¡ reproduced ¨Ñ´à¡çºäÇéã¹ ËÃ×Íá¹Ð¹Óà¢éÒÊÙèÃкºÁÕ¡ÒÃàÃÕ¡ ËÃ×ÍÊè§ ã¹áºº¿ÍÃìÁã´ æ â´ÂËÁÒ¤ÇÒÁÇèÒã´ æ (ÍÔàÅç¡·Ã͹ԡÊì ¡Å ¾ÂÒºÒÅ ºÑ¹·Ö¡ ËÃ×ÍÍÂèÒ§Í×è¹ã´), ËÃ×Í ÊÓËÃѺÇѵ¶Ø »ÃÐʧ¤ìã´ æ â´ÂäÁèÁÕÊÔ·¸Ôì¡ÒÃà¢Õ¹·ÕèÃкآͧ Microsoft Corporation

Microsoft ÍÒ¨ÁÕÊÔ·¸ÔºÑµÃ áÍ»¾ÅÔपѹ patent à¤Ã×èͧËÁÒ¡ÒäéÒ ÅÔ¢ÊÔ·¸Ôì ËÃ×ÍÊÔ·¸Ôã¹·ÃѾÂìÊÔ¹·Ò§»Ñ­­ÒÍ×è¹ æ ¤Ãͺ¤ÅØÁàÃ×èͧàÃ×èͧã¹àÍ¡ÊÒùÕé ¡àÇé¹ÇèÒ expressly â´Âã¹¢é͵¡Å§¡ÒÃÁÕÊÔ·¸Ôì¡ÒÃãªé§Ò¹·ÕèÁÕ¡ÒÃà¢Õ¹ãËé¨Ò¡ Microsoft, furnishing ¢Í§àÍ¡ÊÒùÕéäÁèãËéÊÔ·¸Ôì¡ÒÃãªé§Ò¹ã´ æ ¡ÑºÊÔ·¸ÔºÑµÃàËÅèÒ¹Õé à¤Ã×èͧËÁÒ¡ÒäéÒ ÅÔ¢ÊÔ·¸Ôì ËÃ×Í·ÃѾÂìÊÔ¹·Ò§»Ñ­­ÒÍ×è¹ æ

? 2006 Microsoft Corporation ʧǹÅÔ¢ÊÔ·¸Ôì

, Windows, Windows Server áÅÐ Microsoft SQL Server ÁÕà¤Ã×èͧËÁÒ¡ÒäéÒ·Õèŧ·ÐàºÕ¹ËÃ×Íà¤Ã×èͧËÁÒ¡ÒäéҢͧ Microsoft Corporation ã¹ÊËÃÑ°ÍàÁÃÔ¡ÒáÅÐ/ËÃ×Í»ÃÐà·ÈÍ×è¹