<div>
It is an application that runs automatically based upon triggers in the DB. When new input is received from a client, then it processes the data and writes the results to the DB.<br />
The App server then picks up these results and creates a report for the client.
</div>


It is an application that runs automatically based upon triggers in the DB. When new input is received from a client, then it processes the data and writes the results to the DB.
The App server then picks up these results and creates a report for the client.

<div>
So the answer is still a &quot;Yes&quot;?
</div>


<div>
<div class="content wysiwyg-content">
I have an SQL Cluster with a DB-Active and DB-Passive node. DB-Active is running at around 30% capacity. On my dev server I can run the DB and application without a problem.<br />
So my questions are can I run the application on the passive node?<br />
If yes then do I need to be cautious of anything?<br />
<br />
I know that if the DB-Active fails then it flips to DB-Passive and it should continue to process.<br />
Also that if DB-Passive fails, then my application cannot be run until it is back online.<br />
<br />
Thanks
</div>
</div>


I have an SQL Cluster with a DB-Active and DB-Passive node. DB-Active is running at around 30% capacity. On my dev server I can run the DB and application without a problem.
So my questions are can I run the application on the passive node?
If yes then do I need to be cautious of anything?

I know that if the DB-Active fails then it flips to DB-Passive and it should continue to process.
Also that if DB-Passive fails, then my application cannot be run until it is back online.

Thanks

Running an application on the passive node?

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.