1.       Open up IIS and right-click on the Web Sites node and go to Properties. Click on the Service tab. As shown in FIGURE 1

1.       Check  compress application files checkbox

2.       Check  compress static files checkbox

3.       Go to the Web Service Extensions node. Right-click in the right pane, and click Add a new Web service extension

 

5.       Click on Add. Choose C:\WINDOWS\system32\inetsrv\gzip.dll (your path may be different, but that is doubtful), and click OK. Check the Set extension status to Allowed check box, and click OK.

 

6.       Open up Windows Explorer and go to C:\Windows\System32\inetsrv. Find MetaBase.xml and make a copy (you can just highlight it and do a Ctrl-C, then a Ctrl-P to make a copy of MetaBase.xml). Now open up MetaBase.xml in a text editor.

 

7.        Find the <IIsCompressionScheme/> section. Be careful, there are two sections here: one for deflate and one for gzip. We want gzip so the Location attribute of the element will have the following value:   Location ="/LM/W3SVC/Filters/Compression/gzip"

 

8.       For this example, just add aspx to the HcScriptFileExtensions section as I did, but don’t try to save. It won’t work because the file is locked by default if IIS is running.

9.       Final step is to do an IIS shutdown and restart by right-clicking in Internet Information Services node and then click All Tasks, Restart IIS. You can test at http://www.pipeboost.com, as shown in FIGURE 4.

 

 

SQL Server 2005 provides three main types of replication: snapshot, transactional, and Merge.
Publications and Articles
Articles: database object
Publication: SQL Server group’s articles from the same database in a unit called a publication.
Server Roles
You can configure a server as Publisher, Distributor, and/or Subscriber.

• The Publisher is the original owner of the information that is published.
• A Publisher is the only place where data can be modified.
  

 

The Distributor is responsible for managing the distribution database which stores replication status data, metadata, and, in some replication scenarios, the actual data that SQL Server replicates

A single database server instance can act as both the Publisher and the Distributor.

The server that then receives copies of the publication and provides the data to end users and applications is called the Subscriber.

Subscribers have a read-only copy of the database; in other configurations, you can update information in the Subscribers and replicate those changes back to the Publisher.

Push and Pull Subscriptions

With a push subscription, the Distributor copies the data to the Subscriber database. With a pull subscription, the Subscriber retrieves the data from the Distributor.

When your communication infrastructure has stable and permanent connections among replication servers, a push subscription offers the advantage of providing a central management point to all replication agents that manage the replication process. This results in less administrative overhead and easier troubleshooting procedures.

However, when the replication configuration includes many Subscribers, the distribution process for push subscriptions can tax the hardware resources of a Distributor.

Furthermore, servers or clients that connect on demand are better configured as pull subscriptions.

Replication Types

Snapshot replication the easiest replication type to understand because it is conceptually similar to a full backup and restore.

 

Transactional replication

It makes an initial complete copy of the data, and then all subsequent copies transfer modified data only.

Transactional replication uses the transaction log to apply to the destination data the same transactions performed on the source data. Because the same modifications are applied at both ends, the information is identical at the Publisher and the Subscriber.
This replication type is frequently used for transactional tables, such as an Order Details table in a retail database.

 

Merge replication

When your environment requires the ability to support simultaneous data modifications in the Publisher and Subscriber databases, merge replication offers a solution.

 

Replication Agents

SQL Server uses a group of programs called replication agents to execute the replication process.

To using SQL Server by many department to manage your business you using Use Multiple Instances of SQL Server 2005

SQL Server 2005 supports the capability to install multiple instances (or copies) of SQL Server 2005 or to install SQL Server 2005 alongside earlier versions of SQL Server on the same server. During the installation process, the DBA can choose to install an instance without a name—in which case, the instance name will take the name of the server—as a default instance. To install multiple instances of SQL Server besides the default instance on the same computer, the DBA must give the additional instances different names. Being able to install multiple instances of SQL Server lets you have system and user databases that are independent of each other. This capability not only lets you work with earlier versions of SQL Server already installed on your Computer but also lets you test development software and operate instances of SQL Server 2005 independently of each other.

SQL Server 2005 can support up to 50 instances when it’s not clustered, When SQL Server is clustered, and the maximum number of instances is 25

As to the maximum recommended number of instances, that is going to depend on the resources available on your server and the resources that each instance requires.

Introduction
The configSource attribute was firstly introduced in .NET framework 2.0 to support external configuration files.

After upload website to online server, I need to manage the Website setting from Web.Config, therefore, I save the appSettings, connectionStrings and all settings are needed to manage in Separate XML files, to ease to manage and organize.

This can be done by using configSource attribute,the configSource attribute was firstly introduced in .NET framework 2.0 to support external configuration files. This attribute can be added to any configuration section to specify a an external file for that section. Using an external configuration source can be useful in many scenarios. For instance, you could place a section into an external configSource if you need an easy method to swap settings for the section depending on the environment.

Using the code
First create XML file For Each web.Config section like appSettings.xml, ConnectionString.xml …, and set the file in App_Data Folder to protect.

Copy the each section from web.config and set in XML file as following example: (appSettings.xml)

<?xml version="1.0" standalone="yes"?>
<appSettings>
  <add key="EnableErrorPage" value="false" />
  <add key="RequiredLogin" value="false" />
  <add key="PublicationsEmail" value="email@domain.com" />
  <add key="AdminFromEmail" value="email@domain.com " />
  <add key="AdminToEmail" value="email@domain.com " />
  <add key="SupportEmail" value="email@domain.com" />
</appSettings>

In the Web.config change the appSettings tags to

<appSettings configSource="App_Data\WebConfigXML\appSettings.xml"/>

The configSource attribute must be a relative physical path.

Repeat this for each web.config Section (connectionStrings, smtp,…).

Now you can manage the XML file from secure page by using Gridview control to edit and update the values.

Conclusion
The web.config file is smaller and hence easier to read, and you don't need a complete web.config file for each environment, and help me to manage the website setting.