Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sheena
Starting Member
45 Posts |
 Posted - 2007-04-06 : 02:31:32
|
| I m using sql server 2005 express.I want to create the unique id's and username's for each and every table.For id field if i select the datatype as uniqueidentifier then RowGuid is acitvated what is it ?Indicates whether SQL Server uses the column as a ROWGUID. For id field if i select the datatype as int then Identity Specification is acitvated where i select Yes and increment the id automatically with that Not for Replication is activated what is it ?Indicates whether original identity values are preserved during replication.Need help in simple terms.I could not find exact meaning for what they are used thru search.Thanxs... |
|
|
Vinnie881
Master Smack Fu Yak Hacker
1231 Posts |
Posted - 2007-04-06 : 03:58:41
|
| RowGuid means that it is creating a Row Global Unique Identifier. This means that the ID in that row will be unique throughout your database (and likley anyone elses database). A Identity is a simple autoincrementing value that identifies the column, since the values are incrementing numeric, it will not be unique through your tables or other databases. |
 |
|
|
sheena
Starting Member
45 Posts |
Posted - 2007-04-06 : 13:01:49
|
| thanxs for ur explanation....what is not for replication can u explain me that too..in simple terms.. |
|
|
|
eurob
Posting Yak Master
100 Posts |
Posted - 2007-04-06 : 14:31:04
|
From SQL documentation:quote:
The NOT FOR REPLICATION option is especially useful in transactional or merge replication when a published table is partitioned with rows from various sites. For example, consider a table that contains rows inserted from two sources: Publisher A and Publisher B. The rows inserted at Publisher A are identified by increasing values from 1 through 1000, and those rows at Publisher B are identified by values from 1001 through 2000. If a process at Publisher A inserts a row locally into the table, SQL Server assigns the first row a value of 1, the next row a value of 2, and so forth, in automatically increasing increments. Similarly, if a process at Publisher B inserts a row locally into the table, the first row is assigned a value of 1001, the next row a value of 1002, and so forth. When rows at Publisher A are replicated to B, the identity values remain 1, 2, and so forth, but local seed values at B are not reset.
robert |
|
|
|
|
|
|
|
|
what is rowguid,replication and how used ?