Database

Quote:

SQL

UPDATE  t
...
FROM    Source s
JOIN    Target t WITH(NOLOCK) ON t.id = s.id
...

Avoid using NOLOCK on SQL Server UPDATE and DELETE statements[^]:

SQL

UPDATE t1 
SET t1.x = something
FROM dbo.t1 WITH (NOLOCK)
INNER JOIN ...;

jschell wrote:

Because the key is generated on the client not the server.

public int GetNextPrimaryKey(string collectionName)
{
    lock(_lockObj)
    {
        // Get the PrimaryKeys collection from the DB
        IMongoCollection<PrimaryKeyEntity> pkCol = GetCollection<PrimaryKeyEntity>("PrimaryKeys");

        // Attempt to find the row for the collection 
        PrimaryKeyEntity entity = pkCol.Find(x => x.CollectionName == collectionName).FirstOrDefault();

        // If it doesn't exist...
        if (entity == null)
        {
            // Create and insert the row for the desired collection
            entity = new PrimaryKeyEntity
            {
                PrimaryKey = 1,
                CollectionName = collectionName
            };
            pkCol.InsertOne(entity);
        }
        else
        {
            // Increment the PK
            entity.PrimaryKey = entity.PrimaryKey + 1;

            var filter = Builders<PrimaryKeyEntity>.Filter.Eq(x => x.CollectionName, collectionName);
            var update = Builders<PrimaryKeyEntity>.Update.Set(x => x.PrimaryKey, entity.PrimaryKey);
            var result = pkCol.UpdateOneAsync(filter, update).Result;
        }

        return entity.PrimaryKey;
    }
}

Kevin Marois wrote:

So what if I created a PK table on the sever:

DerekTP123 wrote:

Please, tell me my hosting provider is talking rubbish!

DerekTP123 wrote:

rather than just a later version. It's a real shame, because 15 years ago when I first started using them