This has been a recurring problem. We found script to repair triggers but this keeps coming back. Our system is all 2012 R2 (hyper-V and SC VMM servers).
Microsoft.VirtualManager.DB.CarmineSqlException: Unable to connect to the VMM database because of a general database failure.
Ensure that the SQL Server is running and configured correctly, then try the operation again. ---> System.Data.SqlClient.SqlException: The DELETE statement conflicted with the REFERENCE constraint "FK_tbl_WLC_VAdapter_HWProfile". The conflict occurred
The statement has been terminated.
General statement to pass to your SC product managers:
Dear Microsoft
It's apparent the technology stack including SC and Hyper-V was shipped full of bugs. These seem to be components you build for internal use, andthen ship under the guise of something that works. Who suffers?– we (the customer) do.
The Gen2 templatewas yet another betrayal, a crushed and broken dream.2012 images built on Gen 2 don’t seem to perform the simplest of tasks – make a template and then deploy a VM from template. None of the “run once commands” work.
Hyper-V itself is poor compared to ESX; its uses muchmore disk space to host equivalent data. The notion of differencing disks is a joke, as is shared ISO images. ESX does this by default. I guess we used it because we got it for free, or some
false integration story? LOL - you get what you pay for.
Your own product owners give us misleading and confusing direction on where SC is even going. What is the future of service templates?
Eventually you will get there, I just wish you weren’t testing on customers.
Thanks for your attention to this matter