SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


MDS: Source Control and CI


MDS: Source Control and CI

Author
Message
Phil Parkin
Phil Parkin
SSC Guru
SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)

Group: General Forum Members
Points: 214705 Visits: 24736
Is there anyone out there who has a slick way of managing MDS Models & is prepared to share their experience?

What I am interested in specifically:

* Efficient use of source control to keep a history of MDS models (and, optionally, data in the models)
* Automated deployment of MDS models from source control to QA, Prod etc

Thanks.


Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.

Please surround any code or links you post with the appropriate IFCode formatting tags. It helps readability a lot.
Phil Parkin
Phil Parkin
SSC Guru
SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)

Group: General Forum Members
Points: 214705 Visits: 24736
Bumping this, just in case anyone with any answers missed it the first time.


Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.

Please surround any code or links you post with the appropriate IFCode formatting tags. It helps readability a lot.
Tom OShea
Tom OShea
SSC Veteran
SSC Veteran (236 reputation)SSC Veteran (236 reputation)SSC Veteran (236 reputation)SSC Veteran (236 reputation)SSC Veteran (236 reputation)SSC Veteran (236 reputation)SSC Veteran (236 reputation)SSC Veteran (236 reputation)

Group: General Forum Members
Points: 236 Visits: 465
Bit of info from my experience...

1) MDS is a source control system. you do not need to use anything else. Production MDS is your versioned source control and changes should be made there by business users. This method works best but the MDS FE can be very slow and is a bit unwieldy.

2) If you are looking at some kind of waterfall release process through environments, MDS is definitely not the best tool for this. We automated the export of packages to apply to other environments and then you end up progressing the data through to Prod. It is clunky and causes lots of headaches.

We have used both ways and now only keep the first one.
If you have master data that is changed by IT (and not business) and the changes are released through environments then it is far simpler to just chuck the data in a table with a soft-delete/history process (or something similar).
Phil Parkin
Phil Parkin
SSC Guru
SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)

Group: General Forum Members
Points: 214705 Visits: 24736
Tom OShea - Tuesday, October 9, 2018 6:11 AM
Bit of info from my experience...

1) MDS is a source control system. you do not need to use anything else. Production MDS is your versioned source control and changes should be made there by business users. This method works best but the MDS FE can be very slow and is a bit unwieldy.

2) If you are looking at some kind of waterfall release process through environments, MDS is definitely not the best tool for this. We automated the export of packages to apply to other environments and then you end up progressing the data through to Prod. It is clunky and causes lots of headaches.

We have used both ways and now only keep the first one.
If you have master data that is changed by IT (and not business) and the changes are released through environments then it is far simpler to just chuck the data in a table with a soft-delete/history process (or something similar).

Tom, thanks for your input. I am not interested in source-controlling MDS data. As you suggest, that's what MDS does by itself.

It is the models themselves which are of interest. The entities, subscription views, business rules and permissions, to be more specific. How did you automate their deployment?



Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.

Please surround any code or links you post with the appropriate IFCode formatting tags. It helps readability a lot.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search