RE: SQL Sate: 22012
From: Alejandro Mesa (AlejandroMesa_at_discussions.microsoft.com)
Date: 01/27/05
- Next message: dev-dba in distress on the prod side: "RE: SQL Sate: 22012"
- Previous message: Gert-Jan Strik: "Re: Indexing"
- In reply to: dev-dba in distress on the prod side: "SQL Sate: 22012"
- Next in thread: dev-dba in distress on the prod side: "RE: SQL Sate: 22012"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 27 Jan 2005 12:57:01 -0800
Can you trace which statement is causing the error?
AMB
"dev-dba in distress on the prod side" wrote:
> I'm using SQL 2k, Crystal 9. Restored same database on two servers. Run a
> stored proc that executes the same query. One server returns no records (as
> there are none expected), the other throws a 'Failed to open a rowset SQL
> State: 22012' error, implying divide by zero error, but:
>
> a.) if there are no records, why would it divide by zero
> b.) why wouldn't the result be the same on both servers
>
> In other words, is there a flag or setting that one instance may have that
> would be disregarding that particular type of error?
>
> Thanks in advance,
> SThompson
- Next message: dev-dba in distress on the prod side: "RE: SQL Sate: 22012"
- Previous message: Gert-Jan Strik: "Re: Indexing"
- In reply to: dev-dba in distress on the prod side: "SQL Sate: 22012"
- Next in thread: dev-dba in distress on the prod side: "RE: SQL Sate: 22012"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|