Does moving sites using Content and Structure cause issues in SQL content db's?

Question

I would like to be able to use "manage content and structure" to move sub-sites within a site collection (SharePoint 2010). For example I have a site that is right under my top level site and I would like to move it to be the child site of one of
its' current peers.
There is some concern from admins that this creates a mess in the content DB, therefore all moves should be done using powershell export/import.
Can anyone tell me, technically, what happens when we use the move command in "content and structure" within a site collection and if there are known issues with it?

Answer 1

It doesnot hamper Content DB, all changes are made within the Site Collection Content Database.
using Manage content and structure has benefits, like UI based content restructuring, no support required from Farm Admin. However if you feel to use PowerShell you could still go for it.
Enable developer dashboard, to see what happens in the backgroud while using Manage Content and Structure.
Hope this helps!
Ram - SharePoint Architect
Blog - SharePointDeveloper.in
Please vote or mark your question answered, if my reply helps you