June 21, 2024 at 9:14 am
I have used the 'dbcc clonedatabase' schema-only backup procedure many times in the past to have control over what I want to backup .
Now I have a freshly installed SQL2022 Standard Edition instance that throws the duplicate record error message , like:
Cannot insert duplicate key row in object 'sys.syssingleobjrefs' with unique index 'clst'. The duplicate key value is (6, 51, 0).
I create a connection from within a query window to allow the Dedicated Admin Connection to be able to query the sys.syssingleobjrefs table, but there are simply no user objects created in the model database.
I checked all the objects that have an index 'clst' , but these are all system objects.
When I query the sys.objects table for recent objects created I do find a bunch of Internal Tables that look suspicious though:
ledger_columns_history_internal_history
ledger_tables_history_internal_history
ledger_tables_history_internal
plan_persist_wait_stats_v2
plan_persist_runtime_stats_v2
plan_persist_replicas
db_ledger_digest_locations
ledger_columns_history_internal
Does anyone have a clue how to get this somehow sorted?
Any alternative would be welcome..
June 22, 2024 at 10:10 am
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply