Sharepoint 2007 Language Pack & service pack order

Language packs enable site owners and site collection administrators to create SharePoint sites and site collections in multiple languages without requiring separate installations of Microsoft Office SharePoint Server 2007

You must install the Windows SharePoint Services 3.0 language packs before you install the Office SharePoint Server 2007 language packs.
You must install the language packs in the correct order. The correct order is as follows:

1.Windows SharePoint Services 3.0 language pack
2.Windows SharePoint Services 3.0 SP1 or SP2 language pack
3.Office SharePoint Server 2007 language pack
4.Office SharePoint Server 2007 SP1 or SP2 language pack

 

Important Notes:

  • You must be a member of the Administrators group on the front-end Web server to install these language files. After the language files are installed, the languages are available to all users of the computer.
  • If you are uninstalling a Microsoft Office Server product, you must uninstall all language packs before you uninstall the product.
  • If you are running Service Pack 2 (SP2) of Office SharePoint Server 2007 you only have to download the SP2 language packs. The SP2 language packs include all materials that are in the SP1 language packs.
  • You must download both the Windows SharePoint Services 3.0 language packs and the Office SharePoint Server 2007 language packs.

For each Service Pack do the following :

1. Disconnect users from the server farm by stopping the World Wide Web Publishing service (w3svc) on all Web servers.

2. Begin the software installation on the server hosting the central admin web site

3. At the end of the software update installation, the SharePoint Products and Technologies Configuration Wizard start Note:  If the wizard does not start automatically, click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Products and Technologies Configuration Wizard.

4. On the SharePoint Products and Technologies Configuration Wizard Welcome page, click Next.

5. In the dialog box that notifies you that some services might need to be restarted during configuration, click Yes.

6. On the Completing the SharePoint Products and Technologies Configuration Wizard page, click Next.

7. When the dialog box about installation in a server farm appears, do not click OK. Instead, leave each server with the following dialog box displayed: – THIS IS CRITICAL TO THE SUCCESSFUL INSTALL.
You must run Setup to install new binary files for every server in your server farm. If you have multiple servers in your server farm, run Setup and the configuration wizard on the other servers now, and then return to this server and click OK to continue.

8. When the dialog box from the previous step is displayed on all Web servers in the server farm, use one Web server that hosts the Central Administration Web site to finalize the installation.

9. On the server you selected in the previous step (Step 2), click OK.

10. On the Configuration Successful page, click Finish. 11. Continue updating the remaining computers in the server farm, one at a time, by clicking OK in the dialog box.

 

 

 

For  More Information and Resources:
http://technet.microsoft.com/en-us/library/cc262108(office.12).aspx
http://sharepoint.microsoft.com/Blogs/fromthefield/Lists/Posts/Post.aspx?ID=50

Sharepoint 2010 and various Sql Server versions but which service pack ?

SharePoint 2010 is 64-bit only. It requires Windows Server 2008 SP2 or Windows Server 2008 R2. It will not run on a Server Core installation.It requires one of these versions of x64 SQL Server:

SQL Server 2005 Editions

SQL Server 2005 Enterprise Edition SP3 CU3 (Build 4220) or greater
SQL Server 2005 Standart Edition SP3 CU3 (Build 4220) or greater
SQL Server 2005 Express Edition

(Note: SQL Server 2005 goes out of mainstream support in April 2011)

SQL Server 2008 Editions
SQL Server 2008 Enterprise Edition SP1 CU2 (Build 2714) required , CU5 or later recommended (CU3 & CU4 not recommended)
SQL Server 2008 Standart Edition SP1 CU2 (Build 2714) required , CU5 or later recommended (CU3 & CU4 not recommended)
SQL Server 2008 Express Edition

SQL Server 2008 R2 Enterprise & Standart & Express editions.

How to check version of SQL Server

-- Method 1: Retrieve complete version info, parse results in C#
SELECT @@VERSION AS [SQLVersionInfo];
-- Method 2: Detecting the edition and version of SQL Server from T-SQL
IF SERVERPROPERTY('EngineEdition') = 3
    BEGIN
        PRINT 'Enterprise Edition'
        IF CONVERT(INT, CONVERT(FLOAT,
CONVERT(VARCHAR(3), SERVERPROPERTY('productversion')))) > 9
            BEGIN
                PRINT 'SQL Server 2008 or greater';
                -- Do something like use data compression on an index
            END
        ELSE
            BEGIN
                PRINT 'SQL Server 2005 or lower';
                -- Do something like create an index in online mode
            END
    END
ELSE
    BEGIN
        PRINT 'Standard Edition';
        -- Create an index in offline mode
    END

Compare sql server 2005 and 2008 by SharePoint 2010

You can use both Sql server 2005 and sql server 2008 with sharepoint 2010 but what are the advantages or disadvantages .

Absolutely i recommend use SQL Server 2008 r2 for sharepoint 2010 products. Here is the why i choose it

Performance and Avaiblity :SQL Server 2008 R2 Enterprise edition enables several dimensions on which it can scale, enabling even the most demanding SharePoint Server 2010 deployments. For example, rapidly growing Enterprise Content Management (ECM) or Web Content Management (WCM) workloads may often require compute resources beyond those associated with traditional collaboration scenarios. SQL Server 2008 R2 Enterprise can support this scenario through a number of improvements, by enabling greater processor scale, the ability to address more physical memory on 64-bit hardware, and hot-add hardware support.

Business Continuity Management is a combination of high availability and disaster recovery. High availability ensures a certain absolute degree of operational continuity in the event one or more components fail in an isolated location. Availability requirements are defined by Operating and Service Level Agreements. Disaster recovery ensures a certain absolute degree of operational continuity in the event that all systems fail in one or more locations. Disaster recovery requirements are defined by Operating Level Agreements, Recovery Point, and Recovery Time Objectives.

SQL Server 2008 R2 provides a number of native capabilities to enable the design and deployment of a highly available SharePoint Server 2010 deployment including database mirroring, failover clustering, and log shipping.

SQL Server 2005 mainstream support will end fairly soon (read more athttp://support.microsoft.com/gp/lifesupsps)

Security:
Transparent Data Encryption (TDE) is a feature added in SQL Server 2008 Enterprise that performs real time I/O encryption and decryption of data and log files without requiring unsupported modification of the underlying table schema or increasing the size of the database—that means no changes to SharePoint to enable TDE SQL server audit.Server Audit, which enables tracking and logging events that occur on the system, for example detecting changes or modifications to database objects/stored procedures, surfacing changes to server configuration settings, or detecting changes to audit configuration settings.

Better Reporting Services:SharePoint Server 2010 and SQL Server 2008 R2 Enterprise provide close business intelligence capabilities integration through SQL Server Reporting Services. Using SQL Server Reporting Services, administrators can configure reporting servers to enable real-time access to information and control who has access to that information. End users can benefit from this integration by publishing SQL Server reports directly to Document Libraries or by optionally embedding reports in pages hosted on one or more sites in a Microsoft SharePoint Server 2010 deployment.

To learn more about Reporting Services in SQL Server 2008 see SQL Server Reporting Services (http://msdn.microsoft.com/en-us/library/ms159106.aspx).

Using FileStream Functionality with 2008:Remote Blob Storage integration with SharePoint Server 2010 in SQL Server 2008 R2 Enterprise enables an administrator to externalize SharePoint binary large object (BLOB) data by hosting it on less expensive, commodity hardware solutions and managing it with SQL Server through the same data management techniques they use today. Remote Blob Storage can be an integral component in the most stringent compliance scenarios by enabling third-party technologies to implement solutions such as expunge on the server(s) hosting the externalized BLOBs
see:https://blog.bugrapostaci.com/2010/10/01/sharepoint-2010-server-with-filestream-rbs-provider/

 

Sharepoint Server 2010 Fuctionality and SQL Server Eddition Comparison

Resources:
http://technet.microsoft.com/en-us/library/cc990273.aspx
http://technet.microsoft.com/en-us/library/cc262749.aspx

Other:

http://sqlcat.com/top10lists/archive/2009/02/24/top-10-performance-and-productivity-reasons-to-use-sql-server-2008-for-your-business-intelligence-solutions.aspx



which process lock my dll

Sometimes you want to know whats happinging at the background or wonder which app or process using specific dll. Or may be like me when try to copy a dll getting error “DLL is used by another process” . So what now ?

Process Explorer is one of great tool for this.

Download:

http://download.sysinternals.com/Files/ProcessExplorer.zip

LangStore for Sharepoint 2010

Sharepoint developers knows LangStore for building Multilingual Sharepoint 2007 Sites  by Chris O’Brain. This is very useful tool and i personally thanks Chris for this great tool. But when you want to use this tool with sharepoint 2010 it has some compatiblity issues .
Some of Site columns collide with comming out of the box columns already used by site content type for example “catagory”. I download and change code with schema.xml and element.xml of MultilingualItemType like below:

<FieldRefs>

<FieldRef Name=LinkTitle />

<FieldRef ID={E5C8FDA4-BDA7-4419-8A4E-DE102964884B}
Name=LangStoreCategory Required=true />

<FieldRef ID={D36535DC-31D1-4eb2-9C5C-58CE11EDA226}
Name=LangStoreDescription Required=false />

<FieldRef ID={160036D9-C1A0-419a-AFCE-4CF0525E2160}
Name=LS_LANG_EN Required=false />

<FieldRef ID={21C5A600-9BE5-4f2a-ABD8-271206FC988F}
Name=LS_LANG_TR Required=false />

<FieldRef ID={20DA8826-4CAC-41ca-9399-A82C50E9D66F}
Name=LS_LANG_EN-US Required=false />

<FieldRef ID={1DC99CF7-6667-44ee-83AB-0A5D46D0A092}
Name=LS_LANG_EN-GB Required=false />

<FieldRef ID={600081D6-5AA3-4901-AC55-5537C044D383}
Name=LS_LANG_FR-FR Required=false />

<FieldRef ID={E96813DE-E8A8-4640-AF8D-1E4AC4292B3E}
Name=LS_LANG_DE Required=false />

</FieldRefs>

.

And i also change all project for suitible with Sharepoint 2010 project for VS 2010 IDE.

 

 

Original Langstore :

http://www.sharepointnutsandbolts.com/2008/12/building-multi-lingual-   sharepoint-sites.html

 

Orginal Langstore Download:

http://splanguagestore.codeplex.com/

You can download LangStore2010 from:

http://rapidshare.com/files/425395340/LangStore2010.rar