Wednesday, February 15, 2012

Error message

Hello,
If a execute a query
SELECT '200703' AS Expr1, Zahlungen.KundeID, Zahlungen.Periode,
Zahlungen.Datum, Zahlungen.Betrag, 0 AS Expr2, 0 AS Expr3, 0 AS Expr4, 0 AS
Expr5,
0 AS Expr6, 'U' AS Expr7, Kunde.H_Kanton , Kunde.H_Plz
FROM Zahlungen INNER JOIN
Kunde ON Zahlungen.KundeID = Kunde.ID
WHERE (Zahlungen.Betrag > 0) AND (Zahlungen.Periode = '200703' OR
Zahlungen.Periode = '200713' OR
Zahlungen.Periode = '200613') AND (Zahlungen.KundeID >
0)
I get an error message:
Server: Nachr.-Nr. 3624, Schweregrad 20, Status 1, Zeile 1
Location: p:\sql\ntdbms\storeng\drs\include\record.inl:1447
Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
SPID: 56
Process ID: 296
Die Verbindung wurde unterbrochen.
If I use "TOP 100000" it works fine. If I use TOP 1000000 (million) I get
the error message.
It seams to bee a new problem, because on Tuesday it worked.
Many thanks for your support and best Regards.
StefanPossibly a data corruption. Check out DBCC CHECKDB.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Stefan Braun" <stefan@.braun.name> wrote in message news:58osl6F2hrlctU1@.mid.individual.net...
> Hello,
> If a execute a query
> SELECT '200703' AS Expr1, Zahlungen.KundeID, Zahlungen.Periode,
> Zahlungen.Datum, Zahlungen.Betrag, 0 AS Expr2, 0 AS Expr3, 0 AS Expr4, 0 AS
> Expr5,
> 0 AS Expr6, 'U' AS Expr7, Kunde.H_Kanton , Kunde.H_Plz
> FROM Zahlungen INNER JOIN
> Kunde ON Zahlungen.KundeID = Kunde.ID
> WHERE (Zahlungen.Betrag > 0) AND (Zahlungen.Periode = '200703' OR
> Zahlungen.Periode = '200713' OR
> Zahlungen.Periode = '200613') AND (Zahlungen.KundeID >
> 0)
> I get an error message:
> Server: Nachr.-Nr. 3624, Schweregrad 20, Status 1, Zeile 1
> Location: p:\sql\ntdbms\storeng\drs\include\record.inl:1447
> Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
> SPID: 56
> Process ID: 296
> Die Verbindung wurde unterbrochen.
> If I use "TOP 100000" it works fine. If I use TOP 1000000 (million) I get
> the error message.
> It seams to bee a new problem, because on Tuesday it worked.
> Many thanks for your support and best Regards.
> Stefan
>
>
>

No comments:

Post a Comment