You may be able to package up both paths of the content tree and use something like WinMerge or Kdiff to do a item by item comparison, which might be quick and dirty but may be hard to wade thru especially in instances of inherited fields. I usually like to see if I can use Sitecore Powershell Extensions to complete potentially repeatable tasks like this. ...
While Vandsh's PowerShell script is very nice, I think I would use Unicorn and Beyond Compare. You can configure Unicorn to ignore fields as needed. Once your items are serialized, use Beyond Compare to merge your changes. If you have Unicorn's transparent sync enabled it will automatically pull your changes into Sitecore. Otherwise, you can manually ...
There are a few options included with SPE out-of-the-box which could aid in accomplishing this task. The detail below is produced with SPE 6.0 but much of it was available in previous versions.
There is a Content Report called Items last updated which can be used to find any items in the tree (typically content) that has changed after a specified ...
To answer your questions:
There is no requirement that the Sitecore environments be on different servers, you could have any amount of Sitecore instances available for content consumption.
Changing the target frame shouldn't cause the issues that you are seeing.
The issues are definately centered around MicroChap. Here are the basics with how Content ...
You will need some sort of script to manipulate and transform the data from one form to another. You could do this using some C# code and utilising the Sitecore API but my personal preference would be to use Sitecore PowerShell Extensions as you are planning to do.
In order to "migrate" the data from the old 7.2 instance to the new 8.2 ...
Welcome to Sitecore stackexchange.
RAZL RAZL - can be used to compare the items between two different Sitecore Instances. Please note this is a "paid" software.
Another option is to use Sitecore Courier - This open source module can compare sitecore serialized files in two folders and create a diff (update) package containing the differences.
There is ...
When we need to do this type of content refresh, we generally follow the below steps:
Backup the PROD and QA master databases.
Restore a backup of the PROD master database into the QA database server.
Note: you may need to stop the AppPool for your CM environment to perform this restore.
Deploy the latest code and developer-controlled Sitecore items to ...
Here are a few options you can take:
1- Serialize the Sitecore items you want to move and deserialize on the new instance.
2- Write an SPE script which is what you suggested you are going to do right
3- Use the Razl tool from Hedgehog to compare and move items from one database to the other. You can read more about this here.
Hope this is helpful
I think you could make it work with something similar to what I have here.
# GetItemByUrl function from https://sitecore.stackexchange.com/questions/24962/getting-an-item-using-powershell-having-only-the-url
$url = [System.Uri]::new($url);
$siteContext = [Sitecore.Sites.SiteContextFactory]::GetSiteContext($url.Host, $url....
Disabling statistics when updating the item will improve performance, make sure you don't need this data:
You can also wrap your code with BulkUpdateContext and EventDisabler usings, again, keep in mind that item:saving and item:saved events won't be fired.
For pausing indexing (that will also ...
We regularly move our bacpacs between azure and onsite. It is not unusual for these bacpacs to be greater than 11G. If SSMS is timing out, you may want to try to upload the bacpac to a storage account (Blob storage), then use the portal to create the DB.
If that still bombs, then open a ticket w/Azure folks.
If that works, then it is probably not the ...
To bring data down from the Production environment to UAT and local I would use Sitecore Sidekick Content Migrator.
This is a handy tool that you install in your instances and behind the scene's it uses Rainbow serialization to transfer items from one environment to another.
Once you have it installed, you can set the config up so that each environment has ...
Since you are already on Sitecore 9.0 Initial Update, I don't think you need to create packages and install on Update 2. And obviously since Express Migration Tool 3.1 doesn't support any targeted version greater than 9.0 Initial Version, you can't use that. I would rather Upgrade the same SC 9.0 Initial Version instance to Update 2.
From this stage onward ...