Databases phases and states

Adding more size to Disk in Windows 2003 Cluster environment

After Increasing LUN size in storage It won’t reflect in Windows 2003 environment, to get reflect (Increased size) in Windows 2003 environment it is required to follow below steps.

Before  going to below steps,we need to increase the size LUN which required to add more space.

Once after adding the more space verify the added space in Windows-Disk management.The added space will appear in Disk manager as an unallocated space behind the drive.that means you can extend that particular drive.

refer below link for better understand...
http://support.microsoft.com/kb/325590
 

1.       At a command prompt, type diskpart.exe.

2.       Type list volume to display the existing volumes on the computer.

3.       Type Select volume volume number where volume number is number of the volume that you want to extend.

4.       Type extend [size=n] [disk=n] [noerr]. The following describes the parameters:

size=n
The space, in megabytes (MB), to add to the current partition. If you do not specify a size, the disk is extended to use all the next contiguous unallocated space.
disk=n
The dynamic disk on which to extend the volume. Space equal to size=n is allocated on the disk. If no disk is specified, the volume is extended on the current disk.
noerr
For scripting only. When an error is thrown, this parameter specifies that Diskpart continue to process commands as if the error did not occur. Without the noerr parameter, an error causes Diskpart to exit with an error code.

5.       Type exit to exit Diskpart.exe.

When the extend command is complete, you should receive a message that states that Diskpart successfully extended the volume. The new space should be added to the existing drive while maintaining the data on the volume.

Reference

Microsoft provided a solution with Disk part to merge volumes after increasing size of the LUN 

http://support.microsoft.com/kb/325590

SQL Server version and supported High availabile futures

Ref:  http://msdn.microsoft.com/en-us/library/ms190202.aspx

SQL SERVER TOP STATISTICS

Category	Metric
Largest Single Database	80 TB
Largest Table	20 TB
Biggest total data 1 customer	2.5 PB
Highest transactions per second  1db	36,000
Fastest I/O subsystem in Production	18 GB/Sec
Fastest real time  cube	15 sec latency
Data load for 1 TB	20 min
Largest cube	4.2 TB

Upgrading SQL Server SP3 64bit in Cluster environment ..Good sites

Upgrading  SQL Server SP3 64bit service pack  in Cluster environment  with minimum downtime.

http://www.sqlserverdba.co.cc/2010/04/minimize-downtime-sql-server-2005-sp3.html

Best link for Upgrade SQL Server 2005 SP3 service pack .....

http://www.sqlcoffee.com/Tips0007.htm

http://www.db-staff.com/index.php/microsoft-sql-server/87-upgrade-sql-2005-cluster-to-sp3

DEAD LOCK - WHEN DEAD locks occur (Six reasons)

DEAD LOCK

WHEN DEAD locks occur

1.      Different  transactions trying to accessing the same table object

2.      Log running quires

3.      Lack of proper indexing

4.      Poorly written code

5.      Hardware bottlenecks

6.      Higher Isolation level(other than Read committee)

Moving the users between SQL Servers 2000 to 2005/2008/R2,2005 to 2008/2008R2

Very good link which can support you while migration (especially in Side by Side or New installations)

http://support.microsoft.com/kb/918992

http://support.microsoft.com/kb/246133

http://technet.microsoft.com/en-us/library/ms137870.aspx