June 2008 - Posts
Increasing the efficiency of MigXML is all about making each individual include or exclude pattern as specific as possible and ensuring that the component operates in the proper context. For example, the following component is extremely expensive to include
Read More...
Scanstate and Loadstate both allow the /c switch to be used to skip non-fatal errors. However, due to the impact that using it can have on a migration, great caution must be used when deploying Scanstate and Loadstate with /c. To get started,
Read More...
If you have written a fair amount of migration MigXML you have probably noticed that there are a number of elements that take a context parameter. Do you understand what this parameter controls? Do you understand the impact that it can have on your migration?
Read More...
UPDATE: a post regarding this topic originally went live on 5/29/2008. This was written to clarify some questions that come up in comments I received both online and offline. Although there are a very limited number of scenarios in which USMT can
Read More...
If you have played around with USMT a bit you may have noticed that both Scanstate and Loadstate require that StorePath (the path provided on the command line to where you'd like the migration store placed) be simply a path. However, when creating a compressed
Read More...
