Integrity check fails

Legacy Uncategorised
1

Any ideas of what could cause this to fail in this way?

Task ID: ServerTasks-31110
Task status: Failed
Task queued: Wednesday, September 14, 2016 3:35 PM
Task started: Wednesday, September 14, 2016 3:35 PM
Task duration: less than a second
Server version: 3.4.1+Branch.master.Sha.e8b55c0651d9edede9cac656dace196e18004a0d

                | Failed: Check System Integrity

15:35:39 Error | Schema… [ Failed ]
15:35:39 Info | Orphaned channels… [ Passed ]
15:35:39 Info | Only one unfrozen deployment process per project… [ Passed ]
15:35:39 Fatal | One or more data errors where found.
|
| Running: Schema
15:35:39 Error | Unexpected item: IDX dbo.nci_wi_Deployment_E6DC6B737CFBEB21B1555A1DEF9AD3D4 ChannelId
| Unexpected item: IDX dbo.nci_wi_Deployment_E6DC6B737CFBEB21B1555A1DEF9AD3D4 Created
| Unexpected item: IDX dbo.nci_wi_Deployment_E6DC6B737CFBEB21B1555A1DEF9AD3D4 DeployedBy
| Unexpected item: IDX dbo.nci_wi_Deployment_E6DC6B737CFBEB21B1555A1DEF9AD3D4 DeployedToMachineIds
| Unexpected item: IDX dbo.nci_wi_Deployment_E6DC6B737CFBEB21B1555A1DEF9AD3D4 EnvironmentId
| Unexpected item: IDX dbo.nci_wi_Deployment_E6DC6B737CFBEB21B1555A1DEF9AD3D4 Id
| Unexpected item: IDX dbo.nci_wi_Deployment_E6DC6B737CFBEB21B1555A1DEF9AD3D4 JSON
| Unexpected item: IDX dbo.nci_wi_Deployment_E6DC6B737CFBEB21B1555A1DEF9AD3D4 Name
| Unexpected item: IDX dbo.nci_wi_Deployment_E6DC6B737CFBEB21B1555A1DEF9AD3D4 NONCLUSTERED 0
| Unexpected item: IDX dbo.nci_wi_Deployment_E6DC6B737CFBEB21B1555A1DEF9AD3D4 ProjectGroupId
| Unexpected item: IDX dbo.nci_wi_Deployment_E6DC6B737CFBEB21B1555A1DEF9AD3D4 ProjectId
| Unexpected item: IDX dbo.nci_wi_Deployment_E6DC6B737CFBEB21B1555A1DEF9AD3D4 ReleaseId
| Unexpected item: IDX dbo.nci_wi_Deployment_E6DC6B737CFBEB21B1555A1DEF9AD3D4 TaskId
| Unexpected item: IDX dbo.nci_wi_Deployment_E6DC6B737CFBEB21B1555A1DEF9AD3D4 TenantId
| Unexpected item: IDX dbo.nci_wi_ServerTask_B6A1305A3F620A9ED885DED89F93AD72 CompletedTime
| Unexpected item: IDX dbo.nci_wi_ServerTask_B6A1305A3F620A9ED885DED89F93AD72 Id
| Unexpected item: IDX dbo.nci_wi_ServerTask_B6A1305A3F620A9ED885DED89F93AD72 NONCLUSTERED 0
| Unexpected item: IDX dbo.nci_wi_ServerTask_B6A1305A3F620A9ED885DED89F93AD72 QueueTime
| Unexpected item: IDX dbo.nci_wi_ServerTask_B6A1305A3F620A9ED885DED89F93AD72 StartTime
| Unexpected item: IDX dbo.nci_wi_ServerTask_B6A1305A3F620A9ED885DED89F93AD72 State

2

Hi Chris,

Thanks for reaching out! These errors seem to be coming from some unexpected indexes that we don’t have. Have you added any new indexes manually, or a tool that may have added any automatically?

As a side note: You could also come across issues during an upgrade if you have indexes we don’t expect. If there are any indexes you think are required, let me know and we can see if it would be appropriate to support them!

Kind regards,

Kenny

3

MS has recommended 3, as we have this db on Azure SQL. I had already created the other two, as each of them estimated to save about 2% DTU, meaning about 5% combined performance improvement. I’ve reverted these now, but you might want to consider it! :slight_smile:

[cid:image001.png@01D20F29.50588520]

image001.png
image001.png838×355 18.2 KB

4

Hi Chris,

Thanks for bringing this to our attention. We’ve had some new indexes cause issues recently. We’re currently talking about implementing some changes in a way that would help prevent these types of issues. Indexes are considered very carefully, as we need to make sure adding any won’t negatively effect performance for anyone else. They’re often very specifically targeted to help in certain use cases.

I’ve created a new GitHub issue for your specific Azure recommendation that you can track.

Kind regards,

Kenny

5

Notice:

This issue has been closed due to inactivity. If you encounter the same or a similar issue and require help, please open a new discussion (if we asked for logs or extra details in this thread, consider including them in the new thread). If you are the creator of this thread and believe it should not be closed let us know via our support email.