Firehouse mode

I am getting a message to the effect that a transaction cannot be processes
while SQL Server is in firehouse mode. whazat'Are you talking about some error message regarding a cursor in
*firehose* mode? Can you post the actual error message and the steps
you took to get there?
If you're talking about a firehose cursor message then a firehose cursor
is basically a read-only forward-only cursor. It is the default and
fastest cursor mode for retrieving data from SQL server (when using
cursors that is; but typically set-based queries are faster than
cursor-based queries).
http://msdn.microsoft.com/library/d... />
7_7d6b.asp
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
ncz wrote:

>I am getting a message to the effect that a transaction cannot be processes
>while SQL Server is in firehouse mode. whazat'
>|||Everything Mike said is accurate, so I won't add more detail about WHY it's
happening...
This is most commonly seen in Server Enterprise Manager, when you right
click a table and go "return all rows." Then, after modifying a row, you
can't save the table.
Return the row you want to modify through a query, or better yet, modify the
row from Query Analyzer.
Donna
"ncz" wrote:

> I am getting a message to the effect that a transaction cannot be processe
s
> while SQL Server is in firehouse mode. whazat'|||It basically means that the connection on which you are executing the query
has pending results - i.e. client app has not fetched the last row yet. One
possibility is that you have connection pooling enabled, but your app is not
properly cleaning up resources when queries fail, and leave connections
behind with pending results. The connection is then reused for another spid
and firehose error is raised. Try setting SET XACT_ABORT ON to force SQL to
clean up all resources on SQL error or timeout.
Seach http://support.microsoft.com for "firehose" for additional information
about this error and ways to resolve it.
Adrian
"ncz" <ncz@.discussions.microsoft.com> wrote in message
news:ECE78504-DAFD-4C2E-8762-18A3A02144BB@.microsoft.com...
>I am getting a message to the effect that a transaction cannot be processes
> while SQL Server is in firehouse mode. whazat'