Recommendations on using SQL Server GUID from MS Access

Question

I\'m upsizing an existing MS Access backend to SQL Server 2008 and, because we want to use SQL Server Merge replication, I\'ll have to change all current primary keys (curre

Answer 1

This may be slightly off-topic. However, you do not HAVE to use GUIDs to do merge replication. You can still use your auto-increment integers and allocate different ranges to different database instances. This way rows with identical IDs will not be generated.

Also, there is only one GUID type field in SQL 2008 - uniqueidentifier

Answer 2

Chris is right when saying that (1) you do not need GUIDS for merge replication and (2) there is only one GUID type, but you have to know that:

1. GUIDS can be generated following different rules. You can check this here
2. When setting a replication, SQL will systematically add a GUID (generated as a newsequentialid) to each table if it does not already exist, and will call it rowguid. Of course, if you already have such a GUID/newSequentialId in each table, SQL will make use of it. BUt I do not advise you to 'mix' replication GUIDs with PK GUIDs: you could declare all your primary keys of the GUID type as 'newSequentialIds', but (a) you would then loose the possibility to generate GUID values on the client's side - see infra - and (b) your PKs will then be 'predictable', and this idea makes me feel uncomfortable...
3. keeping autoincrement integers and managing their range through replication means a lot of overhead (you have to allocate ranges for each table/each publication) and a potential source of conflicts when replicating from different sources.
4. Moreover, some SQL bugs like this one, which is specific to range allocation, are still not properly solved: applying cumulative pack 5 did not solve our problem and we had to find another way to restart our replication processes.
5. Anyway, I am deeply convinced that switching from integers to GUIDs as primary keys is mandatory. There are many reasons for that, and one of them is linked to these range management as a potential source for headacke and overnight troubleshouting sessions.

Concerning the change from integers to GUIDS, I advise you to write a step-by-step module that will:

• Backup up all existing tables before modifying them
• Add a GUID field to each table
• Add corresponding FK fields where requested
• Update FK fields through views built with the existing relations (built on integer fields)
• Break relations
• Change PKs from integer fields to GUID fields
• Recreate relations

Take your time to write this code. You will use it many times before having it properly working. You should make profit of the DAO object, tabledefs, indexes, and so on. Keep in mind that you must allways be able to go back to the starting point, so don't forget the initial backup process.

What about manipulating GUIDs from VBA? There are a few things to know about that:

• GUIDs are of the Variant type
• It is possible and easy to generate your GUID as primary key on the client's side of the app, as I proposed it once here.
• When you try to get a GUID value from a control in a form (usually as the linked field in a combobox), you'll get '?????'but no value. You have to refer to the field value in the recordset to get the correct data. You can open such a form in your app, go to the 'immediate' window, and try this:

---

? myForm.myControl
?????

? myForm.recordset.fields("myFieldName")
{000581EB-9CBF-418C-A2D9-5A7141A686CC}

• You might have to convert your guids to strings when navigating through recordsets with expressions such as recordset.findfirst:

---

myFirstRecordset.FindFirst "stringFromGUID(myGuidId) = " & StringFromGUID(mySecondRecordset.Fields("myGuidId").Value)