My BLOG My SHARE My FINDING :)

A SQL Server installation is referred to as an instance. Up to and including SQL Server 7.0, only one installation of SQL Server was possible on a server, but that restriction didn’t suit a number of deployment scenarios that customers required, including high-availability and consolidation. With the release of SQL Server 2000, multiple installations of SQL Server were possible on a single server and were known as SQL Server instances. SQL Server 2008 continues with this model and with very few changes. A default instance has much the same profile that SQL Server installations have had in past; you install SQL Server and then connect using the computer name of the server. Your Windows Server can only have one computer name, so you can only use it to connect to one SQL Server instance. This is called the default instance. If you install additional instances of SQL Server, these are referred to as named instances. You connect to them using the <computername><instanc

People Picker first checks all profiles in the User Information List of the given Site Collection to see if a value in the search match. If a match is found, the value entered is locked, and if you hover your mouse over it, you will see the associated Account Name: If the match is not found then it checks in AD NOTE: User info list is basically from SSP user profile. Is the searching person EID is disable in AD, then People picker won't get him/her in sharepoint  for more info  http://community.bamboosolutions.com/blogs/bambooteamblog/archive/2008/10/09/how-does-person-or-group-column-really-work.aspx

Not able to restore previous version of a aspx page??? It's a known issue that the web parts on your page is not included in your version history and cannot be restored. You may use  field control  instead of web part whenever possible to keep version history. for more info  http://social.msdn.microsoft.com/Forums/en-US/sharepointcustomizationlegacy/thread/ae78f440-c3e8-4a15-8c1d-084bb5f957b4 However you'll be able to restore the content in the publishing pages....not web parts and its contents :(

Nice post look at it http://www.denisstadler.com/sharepoint-2010/sharepoint-2010-publishing-feature/set-up-multilingual-support-in-sharepoint-2010/

Pls look at it http://www.denisstadler.com/sharepoint-2010/language-packs-to-sharepoint-2010/#comments

SharePoint Locale ID (LCID) Table Windows uses a Locale Identifier (LCID) to determine the language and culture to use when displaying information to a user.  The users LCID is picked up from his/her regional settings within windows or from the language settings for the browser.  The application then displays resources, number and date formatting according to the the local.  This post lists a table of LCID's, the short name and full name of each locale. All products, such as SharePoint, SQL, .NET all use this to assist with formatting.  As this post is focusing on LCIDS in SharePoint, there are several folders within the 12 hive that allow you to globalise and localise your application. \BIN\ LCID SharePoint deploys local specific dll's for custom messages used within the SharePoint framework.  You will typically not be updating this folder with your own DLL's. \HCCab \ LCID You are able to create and deploy your own help files that integrate into the SharePoint