On Thu, Mar 20, 2008 at 12:14 PM, Mike yearwood <[EMAIL PROTECTED]>
wrote:
>
> 1 - NewSequentialID is sequential if SQL Server generates the ID.
> That's because SQL Server apparently calls UuidCreateSequential on the
> server. If I have a client generate a GUID using UuidCreateSequential
> the records will be sequential relative to other records on that
> client, but not relative to other clients. Is that a performance
> problem SQL Server?
>
> 2 - If 1 is yes, how can a client ask the Server to perform
> UuidCreateSequential if SQL Server is not on the server?
>
> 3 - Is the NewSequentialID as fast as Nilsson's COMBs?
>
> 4 - Is it better for index storage to have the first part of the GUID
> be static and the second part be sequential or vice versa? Basically
> Surname, Firstname or FirstName, Surname? Is that the same answer for
> SQL and for VFP?
> ---------------------------------------------------
Never use a clustered index on a GUID as your PK. That will stop a lot of
your problems .
Look at the system your creating and determine if your inserting into the
same table in factors of 10 / 1000 / 100,000 a day to define the index that
fits the table.
we get 10 new customers a day and issue 1000 orders that may be as much as
100,000 line items of data per table.
We don't have any kind of a problem with 1600 orders a day and each order my
have a depth in BOM that we generate to be 6 to 10 lines long and in a few
cases it would be 600 to 60000 rows per order.
We use newid() and return that back for secondary use all the time. We are
rarely doing multiple inserts at a time into the same table.
We do a reindex of our high velocity tables weekly because we can!
This is a history of every status change for everything that runs through
our shop floor.
I have a lot of tables that are as simple as this schema:
/****** Object: Table [dbo].[SubmittedOrder St/20/2008 17:15:27
******/
CREATE TABLE [dbo].[SubmittedOrderDocumentStatusHistory](
[guid] [uniqueidentifier] ROWGUIDCOL NOT NULL CONSTRAINT
[DF_SubmittedOrderDocumentStatusHistory_guid] DEFAULT (newid()),
[document] [uniqueidentifier] NOT NULL,
[status] [int] NOT NULL,
[userName] [varchar](50) NOT NULL,
[occurred] [datetime] NOT NULL CONSTRAINT
[DF_SubmittedOrderDocumentStatusHistory_occurred] DEFAULT (getdate()),
CONSTRAINT [PK_SubmittedOrderDocumentStatusHistory] PRIMARY KEY
NONCLUSTERED
(
[guid] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY =
OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]
--
Stephen Russell
Sr. Production Systems Programmer
Mimeo.com
Memphis TN
901.246-0159
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
