One question that is consistently asked by users is about the time values in subscription views. If you look at the “EnterDateTime” and “LastChgDateTime” values in the views, you’ll notice that time may be off by a number of some hours. The difference is due to MDS using UTC when it stores time internally.
Changesets are one of the most useful features in MDS for data management. Confirmation of a proposed change can help prevent mistakes both locally and when “Approval Required” is enabled. The only issue is how do you determine who approved the changeset in MDS?
There is a table for each model that ends in “_CS” to store the changeset information. For example, model 1 would be named “mdm.tbl_1_CS”. This table stores the current status as well as create and update information. There is some other useful information, but the change approver is not listed.
The Message column in “mdm.tblNotificationQueue” does contain that information. It looks like there are separate entries when the changeset status is changed to Pending/Approved and Committed. It would be a lot easier if all of those were in the “_CS” tables.
SELECT b.UserName AS [Approved By],
SUBSTRING(Message, CHARINDEX('<changeset>', Message) + LEN('<changeset>') , CHARINDEX('</changeset>',Message) - (CHARINDEX('<changeset>', Message) + LEN('<changeset>')) ) AS [Changeset] ,
SUBSTRING(Message, CHARINDEX('<new_status>', Message) + LEN('<new_status>') , CHARINDEX('</new_status>',Message) - (CHARINDEX('<new_status>', Message) + LEN('<new_status>')) ) AS [Changeset Status] ,
FROM mdm.tblNotificationQueue a
JOIN mdm.tblUser b ON a.EnterUserID = b.ID
where Message like '%<new_status>Approved</new_status>%'
I’ve been using CrashPlan for Home for a few years now to back up my NAS and a few of my machines. They’ve been great and I’ve never had any issues once I got everything configured. Working in IT and hearing stories about friends losing data led me to follow the 3-2-1 backup rule. Accidents can happen in many different ways and are usually expensive.
About a year ago I received an email from CrashPlan announcing that they were moving away from the personal backup business and focusing on small business. The Home plan was a pretty good deal, and I wouldn’t be able to match the features that their service provided for the price.
A few weeks ago, after some focused procrastination and another email warning about the deadline, I decided to take the easy route and switch to their Small Business account. That option is a little more expensive, but it was a seamless move. It didn’t require any changes at all. I read some reviews of the other comparable services, and it just seemed like a good idea to stay with CrashPlan.
One MDS question that comes up from time to time is how to migrate subscription views during deployments. Manually creating the subscription views can be a time-consuming process. A Version Flag is used to accomplish this task.
Create a Version Flag
1. Under the “Administrative Tasks” section of the home page, select “Version Management.”
2. Select “Flags” under the “Manage” drop-down list.
3. Select the model you are creating a Version Flag. For example, the “Products” sample model contains four Version Flags.
4. You can create a new Version Flag by selecting the model, clicking “Add” and entering a Name. The “Committed Versions Only” value is set to True by default and might need to be updated depending on your needs. Click “Save.”
Assign views to Version Flag
5. The Version Flags have been created and need to be assigned to the Subscription Views. To do this, select “Integration Management” on the home page.
6. Select “Create Views”
7. Select the Subscription Views that you want to update and click “Edit.”
8. Select “Version Flag” from the “Version Option:” list.
9. Select a Version Flag name in the “Version Flag:” list. In this case, the name is “Current.”
10. Click “Save.”
11. The Version Flag value is now populated. Repeat the process for any other entity you want to assign to a version flag.
12. Deploy the model as would typically be done. If you are using the Model Package Editor, make sure you select the Subscription Views.
13. Once the model has been deployed and validated, set the Version Flag to “Current” and click “Save.”
14. Select “Integration Management” on the home page and select “Create Views.”
15. The Subscription Views should now be available for use.