Re: Replication, GUIDs and PKs
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Wed, 20 Sep 2006 09:50:34 -0400
I did a test and guid tables indexes to be 4 times as fragmented as bigint
cols.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Michael MacGregor" <nospam@xxxxxxxxxx> wrote in message
news:uSv8T$O3GHA.1464@xxxxxxxxxxxxxxxxxxxxxxx
To be honest I don't know at this point. I am in the investigation and
analysis stage.
I am trying to pull together a whole bunch of information before I embark
on any monitoring of what is actually going on under the cover. However,
as far as fill factor is concerned, it's set to the default for all
indexes.
Changing the fill factor though can impact read performance, and there are
already some schema design issues that are affecting read performance that
I definitely do not want to become worse.
Also, from a lot of what I have come across so far with regard to the use
of GUIDs as PKs, it is strongly advised not to create a cluster on those
PKs, which makes sense to me. The addition of the sequential GUID in 2005
would seem to have been introduced in order to address the concerns of
using non-sequential GUIDs, however, that particular option is of no use
as the subscriber databases are all 2000, and besides it isn't SQL that is
generating the GUID anyway, but the application.
There are a number of issues with the design, implementation and
maintenance of the databases here that I was brought in to address, but it
would seem that they are related issues and if I change one thing it will
impact another.
Michael MacGregor
Database Architect
.
- Follow-Ups:
- Re: Replication, GUIDs and PKs
- From: Michael MacGregor
- Re: Replication, GUIDs and PKs
- References:
- Replication, GUIDs and PKs
- From: Michael MacGregor
- Re: Replication, GUIDs and PKs
- From: Hilary Cotter
- Re: Replication, GUIDs and PKs
- From: Michael MacGregor
- Re: Replication, GUIDs and PKs
- From: Michael MacGregor
- Re: Replication, GUIDs and PKs
- From: Hilary Cotter
- Re: Replication, GUIDs and PKs
- From: Michael MacGregor
- Re: Replication, GUIDs and PKs
- From: Hilary Cotter
- Re: Replication, GUIDs and PKs
- From: Michael MacGregor
- Re: Replication, GUIDs and PKs
- From: Hilary Cotter
- Re: Replication, GUIDs and PKs
- From: Michael MacGregor
- Re: Replication, GUIDs and PKs
- From: Hilary Cotter
- Re: Replication, GUIDs and PKs
- From: Michael MacGregor
- Replication, GUIDs and PKs
- Prev by Date: Re: SQL Express 4GB size limit
- Next by Date: Make Message failed
- Previous by thread: Re: Replication, GUIDs and PKs
- Next by thread: Re: Replication, GUIDs and PKs
- Index(es):
Relevant Pages
|