|
Home > Archive > MS SQL Data Warehousing > October 2006 > usage of uniqueidentifier as keys fields
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
usage of uniqueidentifier as keys fields
|
|
| .·:m·a·r·l·a:·. 2006-10-25, 6:00 am |
| Hello everyone ::
we would like to ask you a question acording the usage of uniqueidentier as
key fields
we are planning to start designing an application in SQL server which should
have a WEB front end (under .net) and exports of data to other systems
(other SQLs and reporting systems)
the database will include 12 tables with high interpendency among them, few
of them are used as a reference in other tables
the size of the tabla would varie very much, from table with 10-20 line sot
tables with 5thousand lines, maybe 50 thousand, never more
I would like then to ask you what could be the advantage and disadvatage to
use uniqueidentier or create our own keys for the tables, something like
own - good - posibility to easy-read-keys
own - bad -- necesary to create them
uid - good - unique id across tables for sure
uid - good - extandard funcion to generate new ids
uid - bad -- complex unreadable id
besides I would like to ask, how it makes SQL to asure the uniqness of the
uniqueidentier, and what really means a "global id", does it mean that a
given id (by newid()) is anywhere else in the globe used ??
thansk in advance
note :: We have read some documentation acording the uniqueidentier, so we
now the tecnical implications, we would like hear more about the experience
of use or not use it
| |
| Thomas 2006-10-25, 6:00 am |
| http://www.sqlteam.com/item.asp?ItemID=283
--
Thomas
".·:m·a·r·l·a:·." wrote:
> Hello everyone ::
>
> we would like to ask you a question acording the usage of uniqueidentier as
> key fields
>
> we are planning to start designing an application in SQL server which should
> have a WEB front end (under .net) and exports of data to other systems
> (other SQLs and reporting systems)
>
> the database will include 12 tables with high interpendency among them, few
> of them are used as a reference in other tables
>
> the size of the tabla would varie very much, from table with 10-20 line sot
> tables with 5thousand lines, maybe 50 thousand, never more
>
> I would like then to ask you what could be the advantage and disadvatage to
> use uniqueidentier or create our own keys for the tables, something like
> own - good - posibility to easy-read-keys
> own - bad -- necesary to create them
> uid - good - unique id across tables for sure
> uid - good - extandard funcion to generate new ids
> uid - bad -- complex unreadable id
>
>
>
> besides I would like to ask, how it makes SQL to asure the uniqness of the
> uniqueidentier, and what really means a "global id", does it mean that a
> given id (by newid()) is anywhere else in the globe used ??
>
>
> thansk in advance
>
>
> note :: We have read some documentation acording the uniqueidentier, so we
> now the tecnical implications, we would like hear more about the experience
> of use or not use it
>
>
>
|
|
|
|
|