September 4, 2012 at 5:06 am
Hi All,
One of my production databases has 120 tables out of which 104 tables are using GUIDs as clustered indexes. This is a brand new database and we are still in the process of making changes. Looking at the size of the database (30MB) this is not an issue now but this is expected to grow to more than a 100 GB with in a few days time. My only concern is that use of GUIDs causes heavy fragmentation and I am thinking if we can avoid this. Per our developers requirements they cannot use identity values in place of GUIDS. In my scenario what can you think will be a best column that I can have the primary key on.
Thanks for your inputs in advance.
“If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams
September 4, 2012 at 5:20 am
I will also be adding few maintenance jobs on this database that will actually purge data from this database on a daily basis and we are using Entity framework scripts for this application and those huge scripts will be doing heavy inserts and updates on some of these tables daily. So performance is what my major concern is.
“If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams
September 4, 2012 at 5:59 am
Sapen (9/4/2012)
...In my scenario what can you think will be a best column that I can have the primary key on.Thanks for your inputs in advance.
By default primary key creates clustered index.
But you create primary key with non-clustered index and create clustered index on some other column.
September 4, 2012 at 7:34 am
This was removed by the editor as SPAM
September 5, 2012 at 10:35 am
If the keys are generated by a column default, you can use NEWSEQUENTIALID.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply