<div>
By the way, you can use a UNC path in the Output file, so this could write the file straight to the DR server.
</div>


By the way, you can use a UNC path in the Output file, so this could write the file straight to the DR server.

<div>
&gt;&gt; so this could write the file straight to the DR server.<br />
<br />
We replicate our SAN LUNS. Effectively, my data drives from production are mounted against the DR system. Actually, that is how we do our backups. We mount the LUNS and then back them up.<br />
<br />
I will put that into test. Give me a day and I'll award points.
</div>


>> so this could write the file straight to the DR server.

We replicate our SAN LUNS. Effectively, my data drives from production are mounted against the DR system. Actually, that is how we do our backups. We mount the LUNS and then back them up.

I will put that into test. Give me a day and I'll award points.

<div>
<div class="content wysiwyg-content">
We are in the process of upgrading to SQL 2K5 from 2K. <br />
<br />
Our DR plan is such that we take our 2 production SQL servers and combine them into 1 DR SQL Server. One of them becomes the master and then we attach the other databases. I was copying the sysxlogins /syslogins from SQL_2 to a DR info DB and then could import that into the master on SQL_1 at the DR site.<br />
<br />
Withe the change that you can no longer touch the system tables, I'm going to have to resort to using the sp_help_revlogin (<a href="http://support.microsoft.com/kb/918992/" rel="ugc">http://support.microsoft.com/kb/918992/</a>) to transfer users.<br />
<br />
What I'm looking for is some way to write the output to a table in a database other than master or to a text file using a SQL agent job or scheduled task.<br />
<br />
Any ideas?
</div>
</div>


We are in the process of upgrading to SQL 2K5 from 2K. 

Our DR plan is such that we take our 2 production SQL servers and combine them into 1 DR SQL Server. One of them becomes the master and then we attach the other databases. I was copying the sysxlogins /syslogins from SQL_2 to a DR info DB and then could import that into the master on SQL_1 at the DR site.

Withe the change that you can no longer touch the system tables, I'm going to have to resort to using the sp_help_revlogin (http://support.microsoft.com/kb/918992/) to transfer users.

What I'm looking for is some way to write the output to a table in a database other than master or to a text file using a SQL agent job or scheduled task.

Any ideas?

Disaster Recovery Planning -- Migrating Logins

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.

Microsoft SQL Server 2005

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.