¢éͤÇÒÁáÊ´§¢éͼԴ¾ÅÒ´¡ÒÃá¡éä¢: àÁ×èͤس¾ÂÒÂÒÁ·Õè¨ÐãÊè¢éÍÁÙÅã¹ÊÁÒªÔ¡¢Í§¡ÒèÓÅͧẺ¼Êҹ㹠SQL Server 2005: "¢èÒÇÊÒÃà¡ÕèÂǡѺ 548 ÃдѺ 16 ʶҹР2 ºÃ÷Ѵ 1 á·Ã¡ÅéÁàËÅÇ"

¾Ô¨ÒóÒʶҹ¡ÒóìµèÍ仹Õé: ã¹ SQL Server 2005 ¡Ó˹´¤èÒÊÔ觾ÔÁ¾ì¼ÊÒ¹ ¤Ø³à¾ÔèÁµÒÃÒ§·Õè»ÃСͺ´éÇ¡ÒûÃСÒÈ¡ÒüÊÒ¹¤ÍÅÑÁ¹ìÃËÑÊ»ÃШӵÑÇ áÅéÇ ¤Ø³ãÊè¢éÍÁÙÅŧ㹵ÒÃÒ§º¹¼Ùéà¼Âá¾Ãè ¤Ø³«Ô§â¤Ãä¹Êì¢éÍÁÙÅÃÐËÇèÒ§ÊÁÒªÔ¡·Õè¼Ùéà¼Âá¾Ãè áÅШҡ¹Ñé¹ ¤Ø³¾ÂÒÂÒÁ·Õè¨ÐãÊè¢éÍÁÙÅà¾ÔèÁàµÔÁº¹¼Ùéà¼Âá¾Ãè ã¹Ê¶Ò¹¡ÒóìÊÁÁµÔ¹Õé ¤Ø³ä´éÃѺ¢éͤÇÒÁáÊ´§¢éͼԴ¾ÅÒ´µèÍ仹Õ麹¼Ùéà¼Âá¾Ãè:¶éҤس¾ÂÒÂÒÁ àÃÕ¡ãªé sp_adjustpublisheridentityrange ·Õèà¡çº¡Ãкǹ¡ÒÃã¹¼Ùéà¼Âá¾ÃèµÒÁ·Õè¡ÅèÒǶ֧㹢éͤÇÒÁáÊ´§¢éͼԴ¾ÅÒ´ äÁèÊÒÁÒöá¡é䢻ѭËÒ¹Õé

»Ñ­ËÒ¹Õéà¡Ô´¢Öé¹àÁ×èͺÃÔÉÑ·µÑÇá·¹¡ÒüÊÒ¹ËÅÒ«ԧâ¤Ãä¹Êì¢éÍÁÙÅã¹àÇÅÒà´ÕÂǡѹÊÓËÃѺ¡ÒûÃСÒÈàÇÕ¹à´ÕÂǡѹ »Ñ­ËÒ¹ÕéÊÒÁÒö¶Ù¡ exacerbated ¶éҤسÁÕÊÁÒªÔ¡Áҡ㹡ÒûÃСÒÈ¡ÒüÊÒ¹

»Ñ­ËÒ¹Õéà¡Ô´¢Öé¹à¹×èͧ¨Ò¡¤èÒÃËÑÊ»ÃШӵÑǻѨ¨ØºÑ¹¢Í§µÒÃҧ㹼Ùéà¼Âá¾Ãè·ÕèäÁèä´éÍÂÙè㹪èǧ¢Í§¢éÍÁÙÅ੾ÒеÑǢͧ¢éͨӡѴ¡ÒõÃǨÊͺªèǧÃËÑÊ»ÃШӵÑÇ ÅѡɳСÒ÷ӧҹ¹Õéà¡Ô´¢Öé¹àÁ×èͺÃÔÉÑ·µÑÇá·¹¼ÊÒ¹ËÅÒ¾ÂÒÂÒÁ·Õè¨Ðà¾ÔèÁªèǧÃËÑÊ»ÃШӵÑÇã¹àÇÅÒà´ÕÂǡѹä´é â´Â¡ÒÃÊÃéÒ§ªèǧ¶Ñ´ä»¢Í§¢éÍÁÙÅ੾ÒеÑǢͧ¼Ùéà¼Âá¾Ãè

â»Ãá¡ÃÁá¡éä¢ÊÓËÃѺ»Ñ­ËÒ¹Õé¶Ù¡¹ÓÍÍ¡ãªé㹡ÒûÃѺ»Ãا·ÕèÊÐÊÁ 8 ¤ÃÑé§áá ÊÓËÃѺ¢éÍÁÙÅà¾ÔèÁàµÔÁà¡ÕèÂǡѺÇÔ¸Õ¡ÒâÍÃѺ¹Õéᾤࡨâ»Ãá¡ÃÁ»ÃѺ»Ãا·ÕèÊÐÊÁÊÓËÃѺ SQL Server 2005 Service Pack 2 ¤ÅÔ¡ËÁÒÂàÅ¢º·¤ÇÒÁµèÍ仹Õéà¾×èÍ´Ùº·¤ÇÒÁã¹°Ò¹¤ÇÒÁÃÙé¢Í§ Microsoft:ËÁÒÂà˵Ø:à¹×èͧ¨Ò¡ builds ÊÐÊÁ áµèÅÐÃØè¹ãËÁè¢Í§â»Ãá¡ÃÁá¡é䢴èǹ»ÃСͺ´éÇÂâ»Ãá¡ÃÁá¡é䢴èǹ·Ñé§ËÁ´ áÅÐá¡é䢡ÒÃá¡é䢡ÒÃÃÑ¡ÉÒ¤ÇÒÁ»ÅÍ´ÀÑ·Ñé§ËÁ´·ÕèÁÒ¾ÃéÍÁ¡Ñº SQL Server 2005 ¡è͹˹éÒÍÍ¡ Microsoft á¹Ð¹ÓÇèÒ ¤Ø³¤ÇþԨÒóҶ֧¡ÒÃãªéâ»Ãá¡ÃÁá¡é䢴èǹÃØè¹ÅèÒÊØ´·Õè»ÃСͺ´éÇÂâ»Ãá¡ÃÁá¡é䢴èǹ¹Õé ÊÓËÃѺ¢éÍÁÙÅà¾ÔèÁàµÔÁ ãËé¤ÅÔ¡ËÁÒÂàÅ¢º·¤ÇÒÁµèÍ仹Õé à¾×èÍ´Ùº·¤ÇÒÁã¹°Ò¹¤ÇÒÁÃÙé¢Í§ Microsoft::â»Ãá¡ÃÁá¡é䢴èǹ¢Í§ Microsoft SQL Server 2005 ¶Ù¡ÊÃéÒ§ÊÓËÃѺ¡ÒÃÃкآͧ sql server à«ÍÃìÇÔÊá¾ç¤ ¤Ø³µéͧãªéâ»Ãá¡ÃÁá¡é䢴èǹ¢Í§ SQL Server 2005 Service Pack 2 ãËé¡ÒõԴµÑé§ SQL Server 2005 Service Pack 2 â´Â¤èÒàÃÔèÁµé¹ hotfix ·ÕèãËéäÇéã¹ service pack ¢Í§ SQL Server ¨ÐÃÇÁÍÂÙèã¹ service pack ¶Ñ´ä»¢Í§ SQL Server

àÁ×è͵éͧ¡ÒÃá¡é䢻ѭËÒ¹Õé ¤Ø³µéͧ»éͧ¡Ñ¹¨Ð¼ÊÒ¹¡Ñ¹ËÅÒ àÁ×è͵éͧ¡Ò÷Óàªè¹¹Õé à«çµmax_concurrent_merge¤Ø³ÊÁºÑµÔã¹ÊÔ觾ÔÁ¾ìàÇÕ¹â´Â¡ÒÃàÃÕ¡ãªé¤ÓÊÑ觵èÍ仹Õé:ËÁÒÂà˵Ø:ËÅѧ¨Ò¡·Õè¤Ø³ãªéÇÔ¸Õá¡é»Ñ­ËÒ¹Õé ÍҨŴ»ÃÐÊÔ·¸ÔÀÒ¾¡Ò÷ӧҹËÒ¡¤Ø³ÁÕÊÁÒªÔ¡ÁÒ¡ÊÓËÃѺ¡ÒûÃСÒÈ ÅѡɳСÒ÷ӧҹ¹Õéà¡Ô´¢Öé¹à¹×èͧ¨Ò¡ÊÁÒªÔ¡ä´éà¾Õ§˹Öè§ÊÒÁÒö»ÃѺ¢éÍÁÙÅ㹤ÃÑé§à´ÕÂÇ

Microsoft Â×¹ÂѹÇèһѭËÒ¹Õéà»ç¹»Ñ­ËÒ·Õèà¡Ô´¢Ö鹡Ѻ¼ÅÔµÀѳ±ì¢Í§ Microsoft «Öè§ÁÕ¡ÒÃÃкØäÇéã¹Êèǹ "¡ÒÃãªé§Ò¹"

ÇÔ¸Õ¡ÒõÃǨÊͺÇèÒ ¤Ø³¡ÓÅѧ»ÃÐʺ»Ñ­ËÒ¹Õé

¡ÒõÃǨÊͺÇèÒ ¤Ø³¡ÓÅѧ»ÃÐʺ»Ñ­ËÒ¹Õé ´Óà¹Ô¹¡ÒôѧµèÍ仹Õé:

1. µÃǨÊͺÇèÒ ¤èÒÃËÑÊ»ÃШӵÑǻѨ¨ØºÑ¹ÁÕ¢¹Ò´àÅç¡¡ÇèҢͺÅèÒ§¢Í§ªèǧÃËÑÊ»ÃШӵÑÇáá¢Í§¢éͨӡѴ¡ÒõÃǨÊͺªèǧÃËÑÊ»ÃШӵÑÇ
   
   ¡ÒâÍÃѺ¢éÍÁÙÅ੾ÒФèһѨ¨ØºÑ¹ àÃÕ¡ãªé¤ÓÊÑ觵èÍ仹Õé:

   SELECT IDENT_CURRENT ('<TableName>')

   ªèǧ¢éÍÁÙÅ੾ÒеÑǢͧ¢éͨӡѴ¡ÒõÃǨÊͺªèǧÃËÑÊ»ÃШӵÑÇ¡ÒÃÃѺ àÃÕ¡ãªéÍÂèÒ§ã´ÍÂèҧ˹Ö觤ÓÊÑ觵èÍ仹Õé:
   ¤ÓÊÑ觷Õè 1

   sp_helpconstraint '<TableName>'

   ¤ÓÊÑ觷Õè 2

   select * from MSmerge_identity_range
   where is_pub_range <>1
   AND artid IN 
    (select artid from sysmergearticles where name='<TableName>')
   AND subid in 
    (select subid from sysmergesubscriptions  MS
   join sysmergepublications MP 
   on MS.subscriber_server=MP.publisher
   AND MS.db_name = MP.publisher_db
   WHERE name='<PublicationName>'
   )
   

2. ãªé¡ÒÃÊ׺¤é¹¡ÅѺ¢Í§ SQL Server Profiler à¾×èÍ¡Ó˹´ÇèÒ executions interleaved ¢Í§¡Ãкǹ¡Òà sp_MSsetup_publisher_idrange ·Õèà¡çºäÇé¨ÐàÃÔèÁµé¹ â´ÂÃͺàÇÅҢͧºÃÔÉÑ·µÑÇá·¹¡ÒüÊҹᡵèÒ§ËÒ¡ÊÓËÃѺ¡ÒûÃСÒÈ·ÕèàËÁ×͹¡Ñ¹
   
   ÍÂèÒ§äáçµÒÁ executions interleaved ¢Í§¡Ãкǹ¡Òà sp_MSsetup_publisher_idrange ·Õèà¡çºäÇéäÁèàÊÁÍÃкØÇèÒ ¤Ø³¡ÓÅѧ»ÃÐʺ»Ñ­ËÒ¹Õé ¹Õè¤×Í¡ÒÃä´éà¹×èͧ¨Ò¡¶Ù¡äÁèÁÕ¡ÒÃÃѹ SQL Server Profiler àÁ×èÍ occurance à´ÔÁ¢Í§¡Òëԧâ¤Ãä¹Êì¼ÊÒ¹¢éͤÇÒÁáÊ´§¢éͼԴ¾ÅÒ´áá·ÕèÊÃéÒ§¢Öé¹ ÍÂèÒ§äáçµÒÁ executions interleaved ¢Í§¡Ãкǹ¡Òà sp_MSsetup_publisher_idrange à¡çºà¾ÔèÁ¤ÇÒÁà»ç¹ä»ä´é¢Í§»ÃÐʺ»Ñ­ËÒ¹Õé
3. ¤Ø³ÊÒÁÒö¤é¹ËҨмÊÒ¹«é͹·Ñº¡Ñ¹ÍÂÙè·Õèà¡Ô´¢Öé¹àÁ×èͤسä´éÃѺ¢éͤÇÒÁáÊ´§¢éͼԴ¾ÅÒ´ "548" à¡Ô´¢Öé¹ àÁ×è͵éͧ¡Ò÷Óàªè¹¹Õé ¤Ø³ÊÒÁÒöµÃǨ·Ò¹»ÃÐÇѵԡÒÃàÇÕ¹㹰ҹ¢éÍÁÙÅ¡ÒáÃШÒ àÁ×è͵éͧ¡Ò÷Óàªè¹¹Õé àÃÕ¡ãªé¤ÓÊÑ觵èÍ仹Õé:

   Use distribution
   GO
   select session_id, agent_id, B.publication, min(time) as StartTime, max(time) as EndTime
   into #sessiontimes
   from dbo.MSmerge_history A
   join dbo.msmerge_agents B
   on A.agent_id = B.id
   group by session_id, agent_id, publication
   order by 3 desc
   GO
   -- The left side result is the original session. The right side result is the overlapping session.
   select A.*, B.* 
   from #sessiontimes A
   Join #sessiontimes B
   On B.StartTime >= A.StartTime
   AND B.StartTime <= A.EndTime
   AND A.session_id <> B.session_id
   And A.publication=B.publication
   Order By A.StartTime asc
   GO
   drop table #sessiontimes
   

ÇÔ¸Õ¡ÒÃá¡é䢷ÕèÁÕÍÂÙèÃкتèǧÊÓËÃѺµÒÃÒ§·Õè»Ñ­ËÒ·ÕèàÊÕÂËÒÂ

ËÅѧ ¨Ò¡·Õè¤Ø³µÔ´µÑ駡ÒûÃѺ»Ãا·ÕèÊÐÊÁ ËÃ×ÍËÅѧ ¨Ò¡·Õè¤Ø³ãªéÇÔ¸Õ¡Ò÷Õè͸ԺÒÂäÇéã¹Êèǹ¡ÒÃá¡é»Ñ­ËÒ ÁÕªèǧÃËÑÊ»ÃШӵÑÇ·ÕèàÊÕÂËÒ·ÕèÁÕÍÂÙèã¹µÒÃÒ§¨ÐäÁèá¡éä¢ ¤Ø³¨Ðä´éÃѺ¢éͤÇÒÁáÊ´§¢éͼԴ¾ÅÒ´ "548" Âѧ¤§ËÒ¡¤Ø³¾ÂÒÂÒÁá·Ã¡¢éÍÁÙÅŧ㹵ÒÃÒ§ áÅЫԧâ¤Ãä¹Êì¢éÍÁÙÅã¹ÊÁÒªÔ¡ ´Ñ§¹Ñé¹ ¤Ø³µéͧ´éǵ¹àͧá¡é䢪èǧÃËÑÊ»ÃШӵÑÇ·ÕèàÊÕÂËÒ¡ѺµÒÃÒ§ â´ÂãËé·ÓµÒÁ¢Ñ鹵͹µèÍ仹Õé:

ËÁÒÂà˵Ø:¢Ñ鹵͹àËÅèÒ¹Õéà¡ÕèÂÇ¢éͧ´éǵ¹à᷹ͧàÁÅç´¤èһѨ¨ØºÑ¹¢Í§¢éÍÁÙÅ੾ÒÐÊÓËÃѺµÒÃÒ§¶Ù¡µéͧ reseed ¢éÍÁÙÅ੾ÒФèÒ·Õè¼Ùéà¼Âá¾Ãè ã¹Ê¶Ò¹Ð·ÕèàÊÕÂËÒ ¡ÒÃÃкØÁÙŤèһѨ¨ØºÑ¹ÁÕ¢¹Ò´àÅç¡¡ÇèÒªèǧÃËÑÊ»ÃШӵÑÇáá㹡ÒõÃǨÊͺ¨Ó¡Ñ´¼ÊÒ¹¡Òêèǧ¢éÍÁÙÅ੾ÒеÑǨÓÅͧẺ ¢Ñ鹵͹¡ÒÃà¾ÔèÁ¤èÒ identity ÍÂÙèã¹·ÕèÍÂÙèÀÒÂ㹪èǧ¢Í§¢éÍÁÙÅ੾ÒзÕè¡Ó˹´äÇé ´éÇ¡ÒáÒà¤Ã×èͧËÁÒ¨ӡѴ¼ÊÒ¹¡Òêèǧ¢éÍÁÙÅ੾ÒеÑǨÓÅͧẺ ´éǵ¹àͧ These steps assume that identities are configured in an ascending manner and that the identity increment is configured to increase by a value of 1.

1. Confirm that the identity increment value is 1 and that the identity proceeds in ascending manner. You can obtain the identity increment value by running the following statement on the publisher:

   SELECT IDENT_INCR( '<TableName>')

2. Run the following statement on the publisher to find the current identity value on the problematic identity column:

   DBCC CHECKIDENT ('<TableName>')

   After you receive the result, note thecurrent identity valuevalue for comparison in the later steps. ÊѧࡵÇèÒ ¡ÒÃcurrent column valuevalye may be either larger or smaller than thecurrent identity value¤èÒ
   
   ¶éÒ¡ÒÃcurrent column valuevalue is larger than thecurrent identity valuevalue, the column value may have originated at other replications in the topology and merged successfully with the publisher replication. ¶éÒ¡ÒÃcurrent column valuevalue is smaller than thecurrent identity valuevalue, the values may have been inserted on the publisher at a earlier time by using the SET IDENTITY_INSERT ON statement before the merge replication configuration.
3. Run the following statements on the publisher to determine the current identity ranges of the identity range check constraint for the problematic table:

   Use <PublishedDatabaseName>
   GO
   sp_helpconstraint '<TableName>'
   GO
   

   After you receive the result, note the value of theconstraint_keyscolumn of the record where the value of theconstraint_namecolumn is "repl_identity_range_guid". The GUID value corresponds to the value of theartidcolumn for the article in the sysmergearticles system table. To obtain the GUID, run the following statement:

   select artid from sysmergearticles where name = '<TableName>'

   The identity range check constraint spans two separate ranges. The two sets of ranges do not have to be contiguous. For example, the value of theconstraint_keyscolumn can be as follows:
   ([ColumnName]>(1001) AND [ColumnName]<=(2001)></=(2001)>
   OR [ColumnName] > (9001) AND [ColumnName]<>
   ËÁÒÂà˵Ø:This article uses this example to present code in the rest of steps.
   
   In this example, the ranges each span 1,000 values. 1,000 is the default range size. However, you can change the identity range size by using one of the following methods:
   • Specify the@pub_identity_rangeparameter when you run the sp_addmergearticle stored procedure.
   • Change the¢¹Ò´¢Í§ªèǧÊÁÒªÔ¡ä´é¤Ø³ÊÁºÑµÔÊÓËÃѺº·¤ÇÒÁã¹¹Ñ鹺·¤ÇÒÁ¤Ø³ÊÁºÑµÔ¡ÅèͧâµéµÍº
4. ¶éҤس»ÃÐʺ»Ñ­ËÒ·Õè͸ԺÒÂäÇéã¹Êèǹ "ÍÒ¡ÒÃ" ÁÙŤèһѨ¨ØºÑ¹ÃËÑÊ»ÃШӵÑÇ·Õè¤Ø³ºÑ¹·Ö¡äÇéã¹¢Ñ鹵͹·Õè 2 ¤ÇùéÍ¡ÇèҢͺÅèÒ§¢Í§ªèǧÃËÑÊ»ÃШӵÑÇáá¢Í§¢éͨӡѴ¡Òà¤Ã×èͧËÁÒªèǧÃËÑÊ»ÃШӵÑÇ·Õè¤Ø³ºÑ¹·Ö¡äÇéã¹¢Ñ鹵͹·Õè 3
   
   ¶éÒ¤èÒÃËÑÊ»ÃШӵÑǻѨ¨ØºÑ¹ã¹¢Ñ鹵͹·Õè 2 ÁÕ¢¹Ò´ãË­è¡ÇèҢͺº¹¢Í§ªèǧÃËÑÊ»ÃШӵÑÇ·ÕèÊͧ ¢Í§ªèǧÃËÑÊ»ÃШӵÑǵÃǨÊͺ¢éͨӡѴ á¡é䢻ѭËÒ â´ÂãªéÇÔ¸Õ·Õèá¹Ð¹Óã¹¢éͤÇÒÁ¢éͼԴ¾ÅÒ´ ´Ñ§¹Ñé¹ ¤Ø³¤ÇÃÃѹ¡Ãкǹ¡Òà sp_adjustpublisheridentityrange ·Õèà¡çºäÇéã¹¼Ùéà¼Âá¾Ãè
   
   ÊÓËÃѺ¢éÍÁÙÅà¾ÔèÁàµÔÁà¡ÕèÂǡѺ¡Ãкǹ¡Òà sp_adjustpublisheridentityrange à¡çº áÇÐä»·ÕèàÇçºä«µì¢Í§ Microsoft ÊÓËÃѺ¹Ñ¡¾Ñ²¹Òà¤Ã×Í¢èÒ (MSDN) µèÍ仹Õé:
   http://msdn.microsoft.com/en-us/library/ms181527.aspx

   (http://msdn.microsoft.com/en-us/library/ms181527.aspx)
5. àÃÕ¡ãªé¤ÓÊÑ觵èÍ仹Õéà¾×èÍ¡Ó˹´ÇèÒ á¶Çã´ÍÂÙè㹪èǧÃËÑÊ»ÃШӵÑǻѨ¨ØºÑ¹¢Í§¢éͨӡѴ¡ÒõÃǨÊͺªèǧÃËÑÊ»ÃШӵÑÇ:

   SELECT COUNT(*) FROM TableName WHERE 
   ([ColumnName]>(1001) AND [ColumnName]<=(2001) 
   OR [ColumnName]>(9001) AND [ColumnName]<=(10001))
   

   ËÁÒÂà˵Ø
   • ¶éÒ¤ÓÊÑ觷ÕèÊ觡ÅѺ¤èÒ 0 á¶ÇäÁèÁÕÍÂÙè㹪èǧÃËÑÊ»ÃШӵÑǻѨ¨ØºÑ¹ 㹡óչÕé ä»Âѧ¢Ñ鹵͹·Õè 6
   • ¶éÒ¤ÓÊÑ觷ÕèÊ觡ÅѺ¤èÒ·ÕèÁÒ¡¡ÇèÒ 0 àÃÕ¡ãªé¤ÓÊÑ觵èÍ仹Õéà¾×èÍ´Ù¤èÒ¢éÍÁÙÅ੾ÒзÕèÁÒ¡·ÕèÊش㹪èǧÃËÑÊ»ÃШӵÑǻѨ¨ØºÑ¹:

     SELECT MAX(ColumnName) as MaxValue FROM TableName WHERE 
     ([ColumnName]>(1001) AND [ColumnName]<=(2001) OR 
     [ColumnName]>(9001) AND [ColumnName]<=(10001))
     

     ºÑ¹·Ö¡¤èÒÊ觤׹ áÅШҡ¹Ñé¹ ä»·Õè¢Ñ鹵͹·Õè 7
6. ´éǵ¹àͧ reseed ÃËÑÊ»ÃШӵÑǻѨ¨ØºÑ¹ÊÓËÃѺµÒÃÒ§»Ñ­ËÒ·ÕèÍÂÙèã¹·ÕèÍÂÙèÀÒÂ㹪èǧ·Õè¶Ù¡µéͧ
   
   reseed ÃËÑÊ»ÃШӵÑǻѨ¨ØºÑ¹¤èÒµèÓÊØ´¢Í§ªèǧÃËÑÊ»ÃШӵÑǻѨ¨ØºÑ¹ºÇ¡ 1 µÑÇÍÂèÒ§àªè¹ ¶éÒ¤èÒµèÓÊØ´¢Í§ªèǧÃËÑÊ»ÃШӵÑǻѨ¨ØºÑ¹ 1001 ¤èÒ㹪èǧ·Õèà»ç¹ä»ä´éáá¨Ð 1002 à¹×èͧ¨Ò¡¢Õ´¨Ó¡Ñ´´éÒ¹ÅèÒ§¢Í§ªèǧ¢Í§¢éͨӡѴ¡ÒõÃǨÊͺªèǧÃËÑÊ»ÃШӵÑÇ·ÕèãªéÊÙ§¡ÇèÒà¤Ã×èͧËÁÒ (>) àÁ×è͵éͧ¡Ò÷Óàªè¹¹Õé ¡ÒÃàÃÕ¡ãªé¤ÓÊÑ觵èÍ仹Õ麹¼Ùéà¼Âá¾Ãè áÅÐä»·Õè¢Ñ鹵͹·Õè 8 áÅéÇ:

   DBCC CHECKIDENT ('TableName', RESEED, 1002)

7. ´éǵ¹àͧ reseed ÃËÑÊ»ÃШӵÑǻѨ¨ØºÑ¹ÊÓËÃѺµÒÃÒ§»Ñ­ËÒ·ÕèÍÂÙèã¹·ÕèÍÂÙèÀÒÂ㹪èǧ·Õè¶Ù¡µéͧ
   
   ÊÁÁµÔÇèÒ à¾ÔèÁÃËÑÊ»ÃШӵÑǤ×Í 1 reseed ÃËÑÊ»ÃШӵÑǻѨ¨ØºÑ¹à»ç¹¤èÒ·Õè¤Ø³ºÑ¹·Ö¡äÇéã¹¢Ñ鹵͹·Õè 5 áÅÐà¾ÔèÁ 1 áÅéÇ µÑÇÍÂèÒ§àªè¹ ¶éÒ¤èÒ·Õè¤Ø³ºÑ¹·Ö¡äÇéã¹¢Ñ鹵͹·Õè 5 1507, reseed ÃËÑÊ»ÃШӵÑǻѨ¨ØºÑ¹à¾×èÍ 1508 àÁ×è͵éͧ¡Ò÷Óàªè¹¹Õé àÃÕ¡ãªé¤ÓÊÑ觵èÍ仹Õ麹¼Ùéà¼Âá¾Ãè:

   DBCC CHECKIDENT ('TableName', RESEED, 1508)

8. ·Ó¡Ò÷´Êͺà¾×è͵ÃǨÊͺÇèÒ á¶ÇãËÁèÊÒÁÒö¶Ù¡á·Ã¡Å§ã¹µÒÃҧ㹰ҹ¢éÍÁÙŢͧ¼Ùéà¼Âá¾Ãè â´ÂäÁèÁÕ¢éͼԴ¾ÅÒ´ 548 à¡Ô´

For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:ÊÓËÃѺ¢éÍÁÙÅà¾ÔèÁàµÔÁà¡ÕèÂǡѺ¤ÓÈѾ·ì¢Í§¡ÒûÃѺ»Ãا«Í¿µìáÇÃì ãËé¤ÅÔ¡ËÁÒÂàÅ¢º·¤ÇÒÁµèÍ仹Õé à¾×èÍ´Ùº·¤ÇÒÁã¹ Microsoft Knowledge Base::