Lifecycle Management Tool -migrations to 2016
Tracy_Moran
Customer IT Monkey ✭
The concept of the lifecycle management tool is great and is a value add, but my experience is that there is a lot to be desired especially with migrations from 2012 to 2016. Would like to hear from others who have a 2012 to 2016 migration completed or underway and have used the Lifecycle Management Tool. What percentage of your migration was handled by the Lifecycle Management Tool?
0
Answers
I'm not a customer, but I can empathize with some of the nuances in migrating from 2012 to 2016. The LM Tool certainly helps in getting stuff from A to B. How customers have set up 'A' and 'B' can make it tricky! It is certainly worth a chat with our services team to make sure everything is ready for a smooth transition.
Hope that helps!
Steve
We have warehouse issues with SCSM, not sure if it related to the Lifecycle Management Tool yet. If it is related, is it something that has been fixed?
Our issue
The DWDataMart IncidentDIM has no TierQueueID column and the TierQueue column contains GUIDs instead of support group names.
It lists these columns:
SELECT TOP (1000) [IncidentDimKey]
,[BaseManagedEntityId]
,[EntityDimKey]
,[SourceId]
,[TargetResolutionTime]
,[Escalated]
,[Source_IncidentSourceId]
,[Source]
,[Status_IncidentStatusId]
,[Status]
,[ResolutionDescription]
,[NeedsKnowledgeArticle]
,[TierQueue]
,[HasCreatedKnowledgeArticle]
,[LastModifiedSource_IncidentSourceId]
,[LastModifiedSource]
,[Classification_IncidentClassificationId]
,[Classification]
,[ResolutionCategory_IncidentResolutionCategoryId]
,[ResolutionCategory]
,[MessageType]
,[Message]
,[CiresonARA02]
,[AffectedUserClassificationCategory]
,[LegacyReference]
,[ThirdPartyReference]
,[Explanation]
,[FurtherActionRequired]
,[Priority]
,[Impact_IncidentImpactId]
,[Impact]
,[Urgency_IncidentUrgencyId]
,[Urgency]
,[ClosedDate]
,[ResolvedDate]
,[Id]
,[Title]
,[Description]
,[ContactMethod]
,[CreatedDate]
,[ScheduledStartDate]
,[ScheduledEndDate]
,[ActualStartDate]
,[ActualEndDate]
,[IsDowntime]
,[IsParent]
,[ScheduledDowntimeStartDate]
,[ScheduledDowntimeEndDate]
,[ActualDowntimeStartDate]
,[ActualDowntimeEndDate]
,[RequiredBy]
,[PlannedCost]
,[ActualCost]
,[PlannedWork]
,[ActualWork]
,[FirstAssignedDate]
,[FirstResponseDate]
,[DisplayName]
,[AlertId]
,[IsDeleted]
,[InsertedBatchId]
,[UpdatedBatchId]
FROM [DWDataMart].[dbo].[IncidentDim]
Microsoft
They have helped us manually create the TierQueueID and then assisted in introducing a new stored procedure to ensure GUIDs go into the ID column and support group names go into the TierQueue. The downside is it was from the point of the change.
So in our live environment we have this, with the missing ID queue:
SELECT TOP 1000 [IncidentDimKey]
,[TierQueue]
,[TierQueue_IncidentTierQueuesId]
FROM [DWDataMart].[dbo].[IncidentDim]
Possible further issues
We are in the process of introducing new SQL servers for SCSM and DW. We have reinstalled SCSM on the data warehouse management server to point to the new servers. The jobs have run and the above issue is showing. We think that maybe the issue is created by the first sync (if the SCSM 2016 base product doesn't have an issue we are unaware of!?!). We are currently on the UR7 roll up.
Feedback
I would be interested to hear if anyone has experienced any issues with their warehouse like the issue above. Did it involve the Lifecycle Management tool? How did you resolve it? How did you prevent it from occurring again.
Equally, if this sounds familiar and is linked to something else, I would really appreciate hearing from you.