<div>
The easiest way to do this is by using mirroring and a witness server.<br />
<br />
This page has some great points about each method, and how this method is better than just &quot;log shipping&quot;<br />
<br />
I have successfully installed a mirrored witness solution and it is very simple and requires limited cost and/or effort.
</div>


The easiest way to do this is by using mirroring and a witness server.

This page has some great points about each method, and how this method is better than just "log shipping"

I have successfully installed a mirrored witness solution and it is very simple and requires limited cost and/or effort.

<div>
Hi ,,, thanks .. but which page ? 
</div>


<div>
also , is mirroring supported on any hardware ? 
</div>


also , is mirroring supported on any hardware ?

<div>
Yes, mirroring is not hardware dependent, it relies on the setup of the software.
</div>


Yes, mirroring is not hardware dependent, it relies on the setup of the software.

<div>
<div class="content wysiwyg-content">
In our company, we have a SQL 2005 enterprise 64-bit database in primary site and we are planning a DR<br />
site. I had a lot of research in Internet but still cannot make the decision between transactional replication <br />
or log shipping. <br />
what we need is a warm standby in sync with primary ( 30 min behind primary is our SLA) and be able to bring database<br />
up and running in case of a failure.<br />
<br />
here are the options as far as I know :<br />
<br />
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DTS<br />
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Replication<br />
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Clustering<br />
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Backup/Restore<br />
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Log shipping <br />
<br />
I am kind of new to MS SQL ; wanted to get advise from an expert who've done this in a production enviornment.<br />
Really appreciate your help.
</div>
</div>


In our company, we have a SQL 2005 enterprise 64-bit database in primary site and we are planning a DR
site. I had a lot of research in Internet but still cannot make the decision between transactional replication 
or log shipping. 
what we need is a warm standby in sync with primary ( 30 min behind primary is our SLA) and be able to bring database
up and running in case of a failure.

here are the options as far as I know :

•	DTS
•	Replication
•	Clustering
•	 Backup/Restore
•	 Log shipping 

I am kind of new to MS SQL ; wanted to get advise from an expert who've done this in a production enviornment.
Really appreciate your help.

MSSQL 2005 Enterprise warm standby for DR site

Microsoft SQL Server 2005 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. It includes support for managing XML data and allows a database server to be exposed over web services using Tabular Data Stream (TDS) packets encapsulated within SOAP (protocol) requests.