Question

I have a database that is part of a Merge Replication scheme that has a GUID as it’s PK. Specifically the Data Type is uniqueidentifier, Default Value (newsequentialid()), RowGUID is set to Yes. When I do a InsertOnSubmit(CaseNote) I thought I would be able to leave CaseNoteID alone and the database would input the next Sequential GUID like it does if you manually enter a new row in MSSMS. Instead it sends 00000000-0000-0000-0000-000000000000. If I add CaseNoteID = Guid.NewGuid(), the I get a GUID but not a Sequential one (I’m pretty sure).

Is there a way to let SQL create the next sequential id on a LINQ InsertOnSubmit()?

For reference below is the code I am using to insert a new record into the database.

            CaseNote caseNote = new CaseNote                                 {                                     CaseNoteID = Guid.NewGuid(),                                     TimeSpentUnits = Convert.ToDecimal(tbxTimeSpentUnits.Text),                                     IsCaseLog = chkIsCaseLog.Checked,                                     ContactDate = Convert.ToDateTime(datContactDate.Text),                                     ContactDetails = memContactDetails.Text                                 };         caseNotesDB.CaseNotes.InsertOnSubmit(caseNote);          caseNotesDB.SubmitChanges(); 

---

Based on one of the suggestions below I enabled the Autogenerated in LINQ for that column and now I get the following error –> The target table of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause without INTO clause. Ideas?

Answer 1

In the Linq to Sql designer, set the Auto Generated Value property to true for that column.

This is equivalent to the IsDbGenerated property for a column. The only limitation is that you can’t update the value using Linq.