"Get latest" and isolation level serializable conflict
wtjones
Posts: 21
I am using SQL Source Control_2.0.10.4_x86_r155986.exe
After answering all the questions on the "get latest" conflict screen I hit "get latest" to push them out and I was halted on step 2 "Applying schema changes to database" with error:
I opened the SSC generated script via the link on the error screen "Manually edit the script" and noticed this at the beginning:
It is trying to create one of our views that uses OPENROWSET and OLE DB references cannot be used with SERIALIZABLE. I manually changed it to READ COMMITTED and the script worked fine.
Possible solutions:
1) Switch entire file to READ COMMITTED if OPENROWSET is found
2) Move any objects with OPENROWSET into a separate transaction.
After answering all the questions on the "get latest" conflict screen I hit "get latest" to push them out and I was halted on step 2 "Applying schema changes to database" with error:
The requested operation could not be performed because OLE DB provider "Microsoft.ace.OLEDB.12.0" for linked server "(null)" does not support the required transaction interface.
I opened the SSC generated script via the link on the error screen "Manually edit the script" and noticed this at the beginning:
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
It is trying to create one of our views that uses OPENROWSET and OLE DB references cannot be used with SERIALIZABLE. I manually changed it to READ COMMITTED and the script worked fine.
Possible solutions:
1) Switch entire file to READ COMMITTED if OPENROWSET is found
2) Move any objects with OPENROWSET into a separate transaction.
