title: Is it a good idea to use rowguid as unique key in database design?
body: <p>SQL Server provides the type [rowguid]. I like to use this as unique primary key, to identify a row for update. The benefit shows up if you dump the table and reload it, no mess with SerialNo (identity) columns.</p>
  
  <p>In the special case of distributed databases like offline copies on notebooks or something like that, nothing else works. </p>
  
  <p>What do you think? Too much overhead?</p>