May 29, 2009 at 1:13 pm
Hi ,
That's true ..both statements are correct.
It does insert update on DB table as well as its updates some tables on application side
Thanks
ichbinraj
May 29, 2009 at 1:14 pm
Typically for a primary key you want to select the column(s) that uniquely identify the entity and that will be used to JOIN to that table. Also, I'd like to remind you that while SQL Server defaults to a clustered index on the primary key that you can create a non-clustered primary key if it is not the best column for clustering.
Could you post some sample data? Since all your columns are nvarchar it's a little hard to tell what the columns actually contain for data.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
May 29, 2009 at 1:22 pm
Sample data:
300801680051000180023 1W6100757W61 C 2 5 BUTTWELD 5 AIR TO
300801680051000180024 2W6100757W61 C 2 5 BUTTWELD 5 AIR TO
Thanks
Ichbinraj
May 29, 2009 at 1:46 pm
Mmpfft, "BUTTWELD". There's got to be a joke there somewhere. Sorry, late Friday afternoon, I'm in a rare mood - forgive my lame attempt at humor!
-- You can't be late until you show up.
June 1, 2009 at 1:19 pm
hi experts,
Please let me know is it right syntax for creating non cluster index on cluster index ?
CREATE NONCLUSTERED INDEX IX_dbo_ZTable_SID_ITEM_CUSTOM1
ON dbo.Ztable(SID, ITEM_CUSTOM1);
GO
Appreciate your suggestions.
Thanks
ichbinraj
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply