So, the question is how did it affected our solutions.

Solution 1 :
• Create a list template with 60 document.
• Used the above template to create the 200 document library with each library having 60 document for 20 products.
• Individually breaking the item level permission and then adding the custom SharePoint group created for each client X product group, i.e., Client_1_Product_1 to Client_200_Product_20. Which comes to 4000 SharePoint groups.
Problem with Solution 1:
• Whenever we are breaking the item level permission for each item the permission set of the document library was getting copied to the item and as we are adding custom permission to the item, it was getting copied to the list with limited permission.
• So, next time when we were breaking permission for the second item, number of permission were getting incremented with each item.
• As we were not deleting these limited access permission at item level, the drawback is when these item get queried at CQWP it will take lot of time to load the item on the page as SharePoint has to iterate throw all the permission set.

Solution 2 : In the second approach we thought of removing the limited access permission which was getting copied to the item. For this purpose we followed the following path
• Created the list template with 60 document.
• Used the above template to create the 200 document library with each library having 60 document.
• But this time while creating the document library we broke the permission inheritance of the document library and removed all the permission level which was getting copied from Site to the list.
• For item level we were breaking the permission inheritance and checking and deleting any copied permission at item level, before assigning the custom SharePoint group.
Problem with Solution 2:
• Now when we broke the item level permission inheritance nothing from list was getting copied for the first item in the list. But as soon as we add a custom permission to the item the same permission was getting copied to the list holding the item with Limited Access. As we are doing this for one item within the list at a time, with every breaking of permission inheritance at item level and adding of custom permission to the item, it was adding an additional limited Access permission at List level. So, as we were removing the copied permission at item level before assigning the custom permission, with every iteration the number of permission for deletion was getting incremented for each item with each document library.
• This increased the operation time.

Solution 3 : Usage of Temp folder
• Create doc library.
• Break the doc library inheritance to the site. This will copy all the default permissions to the doc library.
• Delete the permission set associated with the doc library.
• Create a temp folder inside the doc library, and break the permission inheritance of that folder.
• Create the list item (document) inside the temp folder. This I am doing to avoid the permission inheritance from the parent list.
• Move the list item from the temp folder to the parent list and this item will have no inherited limited permission because it’s moved from the folder which don’t have any permission.
• Assign the custom SharePoint Group which I have created to the moved list item. This action copies that SharePoint group to the list (SharePoint Feature) with limited access permission.
• After all the documents are created, moved and assigned permission, delete the temp folder.
Problem with Solution 3:
• When we are moving the first item created in the temp folder to the parent list no permission is associated with the item, and as we add a custom permission to the item after breaking the permission inheritance, and that permission getting copied to the list with limited access, the next time we move the second item from temp folder and tried to do the same thing, the limited access permission from list is getting copied to the newly moved list item.
• And with every item moved from the temp folder and process been repeated the number of permission for deletion at time level are getting incremented.
• This increased the operation time.

In all the above scenario we have already created the custom SharePoint Group. This is because for item level permission we want that permission to he available for assignment.

Solution 4 : The successful one. Here we avoided the creation for SharePoint Group beforehand.
• Create doc library.
• Break the doc library inheritance to the site. This will copy all the default permissions to the doc library.
• Delete the permission set associated with the doc library.
• Create a temp folder inside the doc library, and break the permission inheritance of that folder.
• Create the list item (document) inside the temp folder.
• And this process we did for all the 200 document library. Now we had 200 document, with each having on Temp Folder with 60 document without any inherited permission set.
• Now, after the above step we created 4000 custom SharePoint group.
• We picked individual document library, went inside the temp folder, moved the item to the parent list, broke the inheritance, check the copied permission, if there removed it.
• So, for each list we only had 20 permission sets to be removed to a max, starting with zero for the first item.

http://www.andrewconnell.com/blog/archive/2008/07/09/The-Saga-of-an-Ultimate-Virtualization-Rig-Part-1.aspx

http://www.andrewconnell.com/blog/archive/2008/07/09/The-Saga-of-an-Ultimate-Virtualization-Rig-Part-2.aspx

http://www.andrewconnell.com/blog/archive/2008/07/10/The-Saga-of-an-Ultimate-Virtualization-Rig-Part-3.aspx

Creating Custom Quite Virtulization Machine :- http://www.andrewconnell.com/blog/articles/creatingcustomquietvirtualizationrigwithhyperv.aspx

http://www.andrewconnell.com/blog/archive/2009/11/03/doing-sharepoint-2010-development-ndash-whatrsquos-in-your-rig.aspx

http://www.andrewconnell.com/blog/archive/2009/07/23/a-nice-upgrade-to-my-virtualization-rig-ndash-look-mahellip.aspx

http://www.andrewconnell.com/blog/archive/2011/07/10/sharepoint-2010-developmentndashwhatrsquos-in-your-rig.aspx?utm_source=feedburner&utm_medium=email&utm_campaign=Feed%3A+AndrewConnell+%28Andrew+Connell+%5BMVP+SharePoint%5D%29

Content Type Definition : http://msdn.microsoft.com/en-us/library/ms463449.aspx

Base Content Type hierarchy : http://msdn.microsoft.com/en-us/library/ms452896.aspx

Content Types :

- SP 2010 : http://msdn.microsoft.com/en-us/library/ms479905(v=office.14).aspx

- MOSS 2007 : http://msdn.microsoft.com/en-us/library/ms479905(v=office.12).aspx

MOSS Feature
• Portal Site Templates – Additional site templates are especially geared toward centralizing user access to other locations and applications: Enterprise, Corporate Internet presence site, Application Portal Site, and a Roll Up portal site. Enhanced CSS support is also available for extensive corporate branding of portal sites.
• Socialization and Personalization – Offers personalized public My Sites for each user. As well as web parts, such as the SharePoint sites and documents roll up web part (which can list colleagues, friends, and members of a common distribution group), and a social networking web part (which uses information from colleagues’ my site information to aggregate common interests). Convenient content authoring and publishing for users is also available through the browser.
• Enhanced Search – MOSS offers more robust search capabilities across enterprise content sources (sources beyond a single site collection, such as file shares, websites, other SharePoint servers, public folders, and Lotus Notes databases) and supports 200 different file types, relevance ranking, people search, and extensive search indexing administration and control.
• Business Document Management – With additional workflow features built-in (approvals, feedback, and signature collection), MOSS has enhanced document management sites with document libraries that enforce information rights policies with integrated rights management, auditing and retention policies, and legal document processing, as well as record repositories for archiving inactive documents.
• Business Processes and Forms – The enterprise version of MOSS offers enhanced support for business form use and management. Users can fill out Office InfoPath forms from the browser. Integrated heavily with InfoPath 2007, MOSS supports design-once development. It has a Form Import Wizard and centralized forms management and control.
• Business Intelligence – MOSS features an integrated business dashboard that assembles and displays information from different sources. The Enterprise version also offers integrated spreadsheet publishing and management, Excel services, data connection library, business data catalogs, business data web part and actions, a Report Center, and Key Performance Indicators.
• Single Sign-On – This feature integrates with Microsoft systems and line of business applications. It requires a separate credentials database. It allows users to log on to a portal site and have their credentials passed to other backend applications.

_layouts/quiklnch.aspx – Add/Remove/Update the item on the Quick Launch Bar
_layouts/qlreord.aspx – To change the order of the Quick Launch Item.
_layouts/editnav.aspx?ID= – To delete or update the url and the description

MSDN Link – http://msdn.microsoft.com/en-us/library/ms471078.aspx

Regards,
Pradeep Nair

http://blogs.msdn.com/b/ecm/archive/2010/05/14/what-s-new-with-the-content-query-web-part.aspx