TDS (Team Development for Sitecore) makes developer job easy when you’re working with Sitecore. It’s sync all Sitecore data (Content items) among the developers so that everyone is having latest in their local dev. environment. But few clients may not be interested to purchase the license that makes developer job more complex.

Every time you need to give package for your content changes and have to install your colleagues Sitecore packages.

I was impressed with approach what my colleagues implemented in one of the projects

All developers are working in local environment and using the shared network so they installed SQL in one of developers machine and all developers db connections are pointed to single SQL DB

So this way, every content change will be saved in common SQL DB and every one is working on latest.

Kudos to TEAM! Hope you liked the approach.

Update: You don’t have a flexibility to work/ multiple publishes as everyone using shared db. I would suggest to take DB backup for every one week.


Leave a Reply

Your email address will not be published. Required fields are marked *

Related Posts

Fake DB

How to do unit testing for media items in Sitecore + xUnit testing : Fake DB

Unit testing in Sitecore is a tricky one since you need create an items in Fake dB. I didn’t find much information about Media items unit testing and below piece of code may help you! Read more…

Fake DB

PageContext item in Sitecore Fake DB + Unit test cases

I tried to set PageContext using  RenderingContext.EnterContext but didn’t work using (RenderingContext.EnterContext(new Rendering(), contextItem)) { I have set it using  ContextService.Get().Push(pageContext); Here is the code, which may help you using (Db db = new Db using (Db Read more…

Sitecore 8.2

Mocking a reference field in Sitecore Fake DB for Unit test cases

I’m working on Unit test cases and mocking a reference field could be a complex task. Here is the code, which may help you [Fact] public void ReferenceFieldMockingTest() { ID newTemplateId = ID.NewID; ID referenceItemId Read more…