establish duplicate logs

i've got a table like this...
date connected disconnected
10/02/2005 10:03:33 10:05:34
10/02/2005 14:11:00 15:22:01
10/02/2005 14:30 15:00:00
how can i check what connections overlapped in sql?
e.g. result would be (connected at the same time):
10/02/2005 14:11:00 15:22:01
10/02/2005 14:30 15:00:00Nemo
Look at this example ( it will give an idea) written by Itzik Ben-Gan
create table tblConnection
(
StartTimeCon datetime not null,
EndTimeCon datetime not null
)
insert into tblConnection(StartTimeCon,EndTimeCon)va
lues ('20000610
10:00','20000610 10:10')
insert into tblConnection(StartTimeCon,EndTimeCon)va
lues ('20000610
10:20','20000610 10:22')
insert into tblConnection(StartTimeCon,EndTimeCon)va
lues ('20000610
10:23','20000610 10:25')
insert into tblConnection(StartTimeCon,EndTimeCon)va
lues ('20000610
10:27','20000610 10:45')
insert into tblConnection(StartTimeCon,EndTimeCon)va
lues ('20000610
11:57','20000610 12:00')
insert into tblConnection(StartTimeCon,EndTimeCon)va
lues ('20000610
12:01','20000610 12:04')
insert into tblConnection(StartTimeCon,EndTimeCon)va
lues ('20000610
12:04','20000610 12:40')
select * from tblConnection
SELECT
StartTimeCon,
ISNULL(
(SELECT MIN(EndTimeCon)
FROM tblConnection AS S3
WHERE S3.StartTimeCon >= S1.StartTimeCon
AND ISNULL(
DATEDIFF(
minute,
S3.EndTimeCon,
(SELECT MIN(StartTimeCon)
FROM tblConnection AS S4
WHERE S4.StartTimeCon > S3.EndTimeCon)), 5) >= 5),
EndTimeCon) AS EndTimeCon
FROM tblConnection AS S1
WHERE ISNULL(
DATEDIFF(
minute,
(SELECT MAX(EndTimeCon)
FROM tblConnection AS S2
WHERE S2.EndTimeCon < S1.StartTimeCon),S1.StartTimeCon),5) >= 5
"Nemo" <blogmeester@.gmail.com> wrote in message
news:dcqljb$6qs$2@.ctb-nnrp2.saix.net...
> i've got a table like this...
> date connected disconnected
> 10/02/2005 10:03:33 10:05:34
> 10/02/2005 14:11:00 15:22:01
> 10/02/2005 14:30 15:00:00
> how can i check what connections overlapped in sql?
>
> e.g. result would be (connected at the same time):
> 10/02/2005 14:11:00 15:22:01
> 10/02/2005 14:30 15:00:00
>
>
>|||Try,
What format are you using for column [date]?
Is there any primary key in this table that we can use to uniquely identify
each row?

> 10/02/2005
Example:
use northwind
go
create table t1 (
pk_col int not null identity primary key,
[date] varchar(10),
connected char(8),
disconnected char(8)
)
go
insert into t1([date], connected, disconnected) values('10/02/2005',
'10:03:33', '10:05:34')
insert into t1([date], connected, disconnected) values('10/02/2005',
'14:11:00', '15:22:01')
insert into t1([date], connected, disconnected) values('10/02/2005',
'14:30:00', '15:00:00')
go
select * from t1
go
create view dbo.v1
as
select
pk_col, [date], connected, disconnected,
cast(right([date], 4) + '-' + left([date], 2) + '-' + substring([date],
4, 2) + 'T' + connected as datetime) as c1,
cast(right([date], 4) + '-' + left([date], 2) + '-' + substring([date],
4, 2) + 'T' + disconnected as datetime) as c2
from t1
go
select
[date], connected, disconnected
from
dbo.v1 as a
where
exists(select * from dbo.v1 as b where a.pk_col != b.pk_col and a.c1 <=
b.c2 and a.c2 >= b.c1)
or
exists(select * from dbo.v1 as b where a.pk_col != b.pk_col and b.c1 <=
a.c2 and b.c2 >= a.c1)
go
drop view dbo.v1
go
drop table t1
go
AMB
"Nemo" wrote:

> i've got a table like this...
> date connected disconnected
> 10/02/2005 10:03:33 10:05:34
> 10/02/2005 14:11:00 15:22:01
> 10/02/2005 14:30 15:00:00
> how can i check what connections overlapped in sql?
>
> e.g. result would be (connected at the same time):
> 10/02/2005 14:11:00 15:22:01
> 10/02/2005 14:30 15:00:00
>
>
>|||On Wed, 3 Aug 2005 16:50:18 +0200, Nemo wrote:

>i've got a table like this...
>date connected disconnected
>10/02/2005 10:03:33 10:05:34
>10/02/2005 14:11:00 15:22:01
>10/02/2005 14:30 15:00:00
>how can i check what connections overlapped in sql?
>
>e.g. result would be (connected at the same time):
>10/02/2005 14:11:00 15:22:01
>10/02/2005 14:30 15:00:00
Hi Nemo,
Storing date and time in seperate columns is actually not a good idea.
What if a connection begins before midnight, but ends after midnight?
And what if the time between connecting and disconnecting is more than
24 hours?
If you remove the seperate date column and store connected and
disconnected as datetime values, the query to find the overlaps is easy:
SELECT a.connected, a.disconnected
FROM MyTable AS a
WHERE EXISTS
(SELECT *
FROM MyTable AS b
WHERE b.disconnected > a.connected
AND b.connected < a.disconnected)
Depending on your definition of overlap, you might have to change the <
and > operators to <= and >=.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||thanks, followed the advice.
Will combine the date and time fields.
think my table structures nneed some work
regards
Nemo
"Hugo Kornelis" <hugo@.pe_NO_rFact.in_SPAM_fo> wrote in message
news:evb2f1db2obpa231qjk858633q1gvnccj8@.
4ax.com...
> On Wed, 3 Aug 2005 16:50:18 +0200, Nemo wrote:
>
> Hi Nemo,
> Storing date and time in seperate columns is actually not a good idea.
> What if a connection begins before midnight, but ends after midnight?
> And what if the time between connecting and disconnecting is more than
> 24 hours?
> If you remove the seperate date column and store connected and
> disconnected as datetime values, the query to find the overlaps is easy:
> SELECT a.connected, a.disconnected
> FROM MyTable AS a
> WHERE EXISTS
> (SELECT *
> FROM MyTable AS b
> WHERE b.disconnected > a.connected
> AND b.connected < a.disconnected)
> Depending on your definition of overlap, you might have to change the <
> and > operators to <= and >=.
> Best, Hugo
> --
> (Remove _NO_ and _SPAM_ to get my e-mail address)sql

Errors when rebuilding indexes

We have SQL Server 2005 set up and we are seeing the following error messages
in our logs from Daily maintenance Plan.
Please comment on the severity of these errors.
Thanks,
mkb
================================================
Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE =
OFF )
" failed with the following error: "SQL Server detected a logical
consistency-based I/O error: incorrect pageid (expected 1:2676; actual
14616:395852048). It occurred during a read of page (1:2676) in database ID
13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_W ebApp.mdf'. Additional
messages in the SQL Server error log or system event log may provide more
detail. This is a severe error condition that threatens database integrity
and must be corrected immediately. Complete a full database consistency check
(DBCC CHECKDB). This error can be caused by many factors; for more
information, see SQL Server Books Online.
The statement has been terminated.". Possible failure reasons: Problems with
the query, "ResultSet" property not set correctly, parameters not set
correctly, or connection not established correctly.
================================================== =
Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
REORGANIZE WITH ( LOB_COMPACTION = OFF )
" failed with the following error: "SQL Server detected a logical
consistency-based I/O error: incorrect pageid (expected 1:2653; actual
47686:707280961). It occurred during a read of page (1:2653) in database ID
13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_W ebApp.mdf'. Additional
messages in the SQL Server error log or system event log may provide more
detail. This is a severe error condition that threatens database integrity
and must be corrected immediately. Complete a full database consistency check
(DBCC CHECKDB). This error can be caused by many factors; for more
information, see SQL Server Books Online.". Possible failure reasons:
Problems with the query, "ResultSet" property not set correctly, parameters
not set correctly, or connection not established correctly.
================================================== ==
Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
" failed with the following error: "An internal error occurred in DBCC that
prevented further processing. Contact Customer Support Services.
Check terminated. A failure was detected while collecting facts. Possibly
tempdb out of space or a system table is inconsistent. Check previous
errors.". Possible failure reasons: Problems with the query, "ResultSet"
property not set correctly, parameters not set correctly, or connection not
established correctly.
================================================== =
Hi
It seems that there is some corruption in the database. Have you had any
hardware issues? Is there any other information in the SQL Server log or
Windows Event Logs?
You could try dropping the index and running DBCC CHECKDB again. If it works
then re-create the index and run it again. If you don't find out what caused
this then it could happen again.
John
"MKBOBBA" wrote:

> We have SQL Server 2005 set up and we are seeing the following error messages
> in our logs from Daily maintenance Plan.
> Please comment on the severity of these errors.
> Thanks,
> mkb
> ================================================
> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
> REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
> ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE =
> OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2676; actual
> 14616:395852048). It occurred during a read of page (1:2676) in database ID
> 13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_W ebApp.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency check
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.
> The statement has been terminated.". Possible failure reasons: Problems with
> the query, "ResultSet" property not set correctly, parameters not set
> correctly, or connection not established correctly.
>
> ================================================== =
> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
> REORGANIZE WITH ( LOB_COMPACTION = OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2653; actual
> 47686:707280961). It occurred during a read of page (1:2653) in database ID
> 13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_W ebApp.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency check
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.". Possible failure reasons:
> Problems with the query, "ResultSet" property not set correctly, parameters
> not set correctly, or connection not established correctly.
> ================================================== ==
> Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
> " failed with the following error: "An internal error occurred in DBCC that
> prevented further processing. Contact Customer Support Services.
> Check terminated. A failure was detected while collecting facts. Possibly
> tempdb out of space or a system table is inconsistent. Check previous
> errors.". Possible failure reasons: Problems with the query, "ResultSet"
> property not set correctly, parameters not set correctly, or connection not
> established correctly.
> ================================================== =
>
|||And I forgot to add.. Make sure you have a good backup before doing this! You
could try restoring a backup on a different machine to try your tests out
before working on live (providing you have the hardware!)
John
"MKBOBBA" wrote:

> We have SQL Server 2005 set up and we are seeing the following error messages
> in our logs from Daily maintenance Plan.
> Please comment on the severity of these errors.
> Thanks,
> mkb
> ================================================
> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
> REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
> ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE =
> OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2676; actual
> 14616:395852048). It occurred during a read of page (1:2676) in database ID
> 13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_W ebApp.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency check
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.
> The statement has been terminated.". Possible failure reasons: Problems with
> the query, "ResultSet" property not set correctly, parameters not set
> correctly, or connection not established correctly.
>
> ================================================== =
> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
> REORGANIZE WITH ( LOB_COMPACTION = OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2653; actual
> 47686:707280961). It occurred during a read of page (1:2653) in database ID
> 13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_W ebApp.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency check
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.". Possible failure reasons:
> Problems with the query, "ResultSet" property not set correctly, parameters
> not set correctly, or connection not established correctly.
> ================================================== ==
> Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
> " failed with the following error: "An internal error occurred in DBCC that
> prevented further processing. Contact Customer Support Services.
> Check terminated. A failure was detected while collecting facts. Possibly
> tempdb out of space or a system table is inconsistent. Check previous
> errors.". Possible failure reasons: Problems with the query, "ResultSet"
> property not set correctly, parameters not set correctly, or connection not
> established correctly.
> ================================================== =
>

Errors when rebuilding indexes

We have SQL Server 2005 set up and we are seeing the following error messages
in our logs from Daily maintenance Plan.
Please comment on the severity of these errors.
Thanks,
mkb
================================================ Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE = OFF )
" failed with the following error: "SQL Server detected a logical
consistency-based I/O error: incorrect pageid (expected 1:2676; actual
14616:395852048). It occurred during a read of page (1:2676) in database ID
13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_WebApp.mdf'. Additional
messages in the SQL Server error log or system event log may provide more
detail. This is a severe error condition that threatens database integrity
and must be corrected immediately. Complete a full database consistency check
(DBCC CHECKDB). This error can be caused by many factors; for more
information, see SQL Server Books Online.
The statement has been terminated.". Possible failure reasons: Problems with
the query, "ResultSet" property not set correctly, parameters not set
correctly, or connection not established correctly.
===================================================
Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
REORGANIZE WITH ( LOB_COMPACTION = OFF )
" failed with the following error: "SQL Server detected a logical
consistency-based I/O error: incorrect pageid (expected 1:2653; actual
47686:707280961). It occurred during a read of page (1:2653) in database ID
13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_WebApp.mdf'. Additional
messages in the SQL Server error log or system event log may provide more
detail. This is a severe error condition that threatens database integrity
and must be corrected immediately. Complete a full database consistency check
(DBCC CHECKDB). This error can be caused by many factors; for more
information, see SQL Server Books Online.". Possible failure reasons:
Problems with the query, "ResultSet" property not set correctly, parameters
not set correctly, or connection not established correctly.
====================================================
Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
" failed with the following error: "An internal error occurred in DBCC that
prevented further processing. Contact Customer Support Services.
Check terminated. A failure was detected while collecting facts. Possibly
tempdb out of space or a system table is inconsistent. Check previous
errors.". Possible failure reasons: Problems with the query, "ResultSet"
property not set correctly, parameters not set correctly, or connection not
established correctly.
===================================================Hi
It seems that there is some corruption in the database. Have you had any
hardware issues? Is there any other information in the SQL Server log or
Windows Event Logs?
You could try dropping the index and running DBCC CHECKDB again. If it works
then re-create the index and run it again. If you don't find out what caused
this then it could happen again.
John
"MKBOBBA" wrote:
> We have SQL Server 2005 set up and we are seeing the following error messages
> in our logs from Daily maintenance Plan.
> Please comment on the severity of these errors.
> Thanks,
> mkb
> ================================================> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
> REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
> ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE => OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2676; actual
> 14616:395852048). It occurred during a read of page (1:2676) in database ID
> 13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_WebApp.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency check
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.
> The statement has been terminated.". Possible failure reasons: Problems with
> the query, "ResultSet" property not set correctly, parameters not set
> correctly, or connection not established correctly.
>
> ===================================================> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
> REORGANIZE WITH ( LOB_COMPACTION = OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2653; actual
> 47686:707280961). It occurred during a read of page (1:2653) in database ID
> 13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_WebApp.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency check
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.". Possible failure reasons:
> Problems with the query, "ResultSet" property not set correctly, parameters
> not set correctly, or connection not established correctly.
> ====================================================> Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
> " failed with the following error: "An internal error occurred in DBCC that
> prevented further processing. Contact Customer Support Services.
> Check terminated. A failure was detected while collecting facts. Possibly
> tempdb out of space or a system table is inconsistent. Check previous
> errors.". Possible failure reasons: Problems with the query, "ResultSet"
> property not set correctly, parameters not set correctly, or connection not
> established correctly.
> ===================================================>|||And I forgot to add.. Make sure you have a good backup before doing this! You
could try restoring a backup on a different machine to try your tests out
before working on live (providing you have the hardware!)
John
"MKBOBBA" wrote:
> We have SQL Server 2005 set up and we are seeing the following error messages
> in our logs from Daily maintenance Plan.
> Please comment on the severity of these errors.
> Thanks,
> mkb
> ================================================> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
> REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
> ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE => OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2676; actual
> 14616:395852048). It occurred during a read of page (1:2676) in database ID
> 13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_WebApp.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency check
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.
> The statement has been terminated.". Possible failure reasons: Problems with
> the query, "ResultSet" property not set correctly, parameters not set
> correctly, or connection not established correctly.
>
> ===================================================> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
> REORGANIZE WITH ( LOB_COMPACTION = OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2653; actual
> 47686:707280961). It occurred during a read of page (1:2653) in database ID
> 13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_WebApp.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency check
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.". Possible failure reasons:
> Problems with the query, "ResultSet" property not set correctly, parameters
> not set correctly, or connection not established correctly.
> ====================================================> Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
> " failed with the following error: "An internal error occurred in DBCC that
> prevented further processing. Contact Customer Support Services.
> Check terminated. A failure was detected while collecting facts. Possibly
> tempdb out of space or a system table is inconsistent. Check previous
> errors.". Possible failure reasons: Problems with the query, "ResultSet"
> property not set correctly, parameters not set correctly, or connection not
> established correctly.
> ===================================================>

Errors when rebuilding indexes

We have SQL Server 2005 set up and we are seeing the following error message
s
in our logs from Daily maintenance Plan.
Please comment on the severity of these errors.
Thanks,
mkb
========================================
========
Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllU
serData]
REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE
=
OFF )
" failed with the following error: "SQL Server detected a logical
consistency-based I/O error: incorrect pageid (expected 1:2676; actual
14616:395852048). It occurred during a read of page (1:2676) in database ID
13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
Server\\MSSQL. 1\\MSSQL\\DATA\\SP_IntranetMySites_WebAp
p.mdf'. Additional
messages in the SQL Server error log or system event log may provide more
detail. This is a severe error condition that threatens database integrity
and must be corrected immediately. Complete a full database consistency chec
k
(DBCC CHECKDB). This error can be caused by many factors; for more
information, see SQL Server Books Online.
The statement has been terminated.". Possible failure reasons: Problems with
the query, "ResultSet" property not set correctly, parameters not set
correctly, or connection not established correctly.
========================================
===========
Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllU
serData]
REORGANIZE WITH ( LOB_COMPACTION = OFF )
" failed with the following error: "SQL Server detected a logical
consistency-based I/O error: incorrect pageid (expected 1:2653; actual
47686:707280961). It occurred during a read of page (1:2653) in database ID
13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
Server\\MSSQL. 1\\MSSQL\\DATA\\SP_IntranetMySites_WebAp
p.mdf'. Additional
messages in the SQL Server error log or system event log may provide more
detail. This is a severe error condition that threatens database integrity
and must be corrected immediately. Complete a full database consistency chec
k
(DBCC CHECKDB). This error can be caused by many factors; for more
information, see SQL Server Books Online.". Possible failure reasons:
Problems with the query, "ResultSet" property not set correctly, parameters
not set correctly, or connection not established correctly.
========================================
============
Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
" failed with the following error: "An internal error occurred in DBCC that
prevented further processing. Contact Customer Support Services.
Check terminated. A failure was detected while collecting facts. Possibly
tempdb out of space or a system table is inconsistent. Check previous
errors.". Possible failure reasons: Problems with the query, "ResultSet"
property not set correctly, parameters not set correctly, or connection not
established correctly.
========================================
===========Hi
It seems that there is some corruption in the database. Have you had any
hardware issues? Is there any other information in the SQL Server log or
Windows Event Logs?
You could try dropping the index and running DBCC CHECKDB again. If it works
then re-create the index and run it again. If you don't find out what caused
this then it could happen again.
John
"MKBOBBA" wrote:

> We have SQL Server 2005 set up and we are seeing the following error messa
ges
> in our logs from Daily maintenance Plan.
> Please comment on the severity of these errors.
> Thanks,
> mkb
> ========================================
========
> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[Al
lUserData]
> REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
> ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLIN
E =
> OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2676; actual
> 14616:395852048). It occurred during a read of page (1:2676) in database I
D
> 13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL. 1\\MSSQL\\DATA\\SP_IntranetMySites_WebAp
p.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency ch
eck
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.
> The statement has been terminated.". Possible failure reasons: Problems wi
th
> the query, "ResultSet" property not set correctly, parameters not set
> correctly, or connection not established correctly.
>
> ========================================
===========
> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[Al
lUserData]
> REORGANIZE WITH ( LOB_COMPACTION = OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2653; actual
> 47686:707280961). It occurred during a read of page (1:2653) in database I
D
> 13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL. 1\\MSSQL\\DATA\\SP_IntranetMySites_WebAp
p.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency ch
eck
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.". Possible failure reasons:
> Problems with the query, "ResultSet" property not set correctly, parameter
s
> not set correctly, or connection not established correctly.
> ========================================
============
> Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
> " failed with the following error: "An internal error occurred in DBCC tha
t
> prevented further processing. Contact Customer Support Services.
> Check terminated. A failure was detected while collecting facts. Possibly
> tempdb out of space or a system table is inconsistent. Check previous
> errors.". Possible failure reasons: Problems with the query, "ResultSet"
> property not set correctly, parameters not set correctly, or connection no
t
> established correctly.
> ========================================
===========
>|||And I forgot to add.. Make sure you have a good backup before doing this! Yo
u
could try restoring a backup on a different machine to try your tests out
before working on live (providing you have the hardware!)
John
"MKBOBBA" wrote:

> We have SQL Server 2005 set up and we are seeing the following error messa
ges
> in our logs from Daily maintenance Plan.
> Please comment on the severity of these errors.
> Thanks,
> mkb
> ========================================
========
> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[Al
lUserData]
> REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
> ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLIN
E =
> OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2676; actual
> 14616:395852048). It occurred during a read of page (1:2676) in database I
D
> 13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL. 1\\MSSQL\\DATA\\SP_IntranetMySites_WebAp
p.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency ch
eck
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.
> The statement has been terminated.". Possible failure reasons: Problems wi
th
> the query, "ResultSet" property not set correctly, parameters not set
> correctly, or connection not established correctly.
>
> ========================================
===========
> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[Al
lUserData]
> REORGANIZE WITH ( LOB_COMPACTION = OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2653; actual
> 47686:707280961). It occurred during a read of page (1:2653) in database I
D
> 13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL. 1\\MSSQL\\DATA\\SP_IntranetMySites_WebAp
p.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency ch
eck
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.". Possible failure reasons:
> Problems with the query, "ResultSet" property not set correctly, parameter
s
> not set correctly, or connection not established correctly.
> ========================================
============
> Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
> " failed with the following error: "An internal error occurred in DBCC tha
t
> prevented further processing. Contact Customer Support Services.
> Check terminated. A failure was detected while collecting facts. Possibly
> tempdb out of space or a system table is inconsistent. Check previous
> errors.". Possible failure reasons: Problems with the query, "ResultSet"
> property not set correctly, parameters not set correctly, or connection no
t
> established correctly.
> ========================================
===========
>sql

errors to log

what a want to know is if there s a way to log sql server errors on a log file, table, these errors are not sql server logs which already exists, i want to log dead locks, sql server timeout errors vs on sql server or somewhere.

is it possible ?

may i use sql server profiler for that purpose?

thx in advance..

You can set up SQL Server Alerts that can log to the Application Event Log, or you could write some custom code to log intersing information to a SQL Server database table.

Errors restoring Transaction Logs

Howdy,
I just accidently wiped out a table that had some pretty important data in
it. Can I restore it from the transaction log? Here's what I've tried so far
and I get the errors as stated below. I did do "net pause mssqlserver"
before running it.
USE master
RESTORE DATABASE cpts
FROM DISK = 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\RPCS.mdf'
WITH RECOVERY
RESTORE LOG cpts
FROM DISK = 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\Copy of
RPCS.ldf'
WITH RECOVERY, STOPAT = 'Apr 24, 2006 5:20 PM'
Erros
Server: Msg 3101, Level 16, State 2, Line 3
Exclusive access could not be obtained because the database is in use.
Server: Msg 3013, Level 16, State 1, Line 3
RESTORE DATABASE is terminating abnormally.
Server: Msg 3101, Level 16, State 2, Line 7
Exclusive access could not be obtained because the database is in use.
Server: Msg 3013, Level 16, State 1, Line 7
RESTORE LOG is terminating abnormally.
Thanks!!
David LozziYour database cpts will need to be changed to single user mode.
EXEC master.dbo.sp_dboption 'cpts', 'single user', true
(Be reminded to set it to false afterwards.)
Martin C K Poon
Senior Analyst Programmer
====================================
"David Lozzi" <dlozzi@.nospam.nospam> bl
news:u6smwZ$ZGHA.1196@.TK2MSFTNGP03.phx.gbl g...
> Howdy,
> I just accidently wiped out a table that had some pretty important data in
> it. Can I restore it from the transaction log? Here's what I've tried so
far
> and I get the errors as stated below. I did do "net pause mssqlserver"
> before running it.
> USE master
> RESTORE DATABASE cpts
> FROM DISK = 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\RPCS.mdf'
> WITH RECOVERY
> RESTORE LOG cpts
> FROM DISK = 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\Copy of
> RPCS.ldf'
> WITH RECOVERY, STOPAT = 'Apr 24, 2006 5:20 PM'
>
> Erros
> Server: Msg 3101, Level 16, State 2, Line 3
> Exclusive access could not be obtained because the database is in use.
> Server: Msg 3013, Level 16, State 1, Line 3
> RESTORE DATABASE is terminating abnormally.
> Server: Msg 3101, Level 16, State 2, Line 7
> Exclusive access could not be obtained because the database is in use.
> Server: Msg 3013, Level 16, State 1, Line 7
> RESTORE LOG is terminating abnormally.
> Thanks!!
> David Lozzi
>|||Pausing the service only prevents new server connections; existing
connections to the database are not affected.
You'll need to kill connections to the database before you can restore.
With SQL 2000 and above, you can do this easily with ALTER DATABASE ...
ROLLBACK IMMEDIATE:
ALTER DATABASE MyDatabase
SET SINGLE_USER
WITH ROLLBACK IMMEDIATE
Note that you don't necessarily need to overwrite the existing database to
recovery the lost data. An alternative is to restore to a different
database name (and different file names) so you can extract the lost data.
However, if related tables have been modified since the problem, you might
find it easier to overwrite the existing database,
Hope this helps.
Dan Guzman
SQL Server MVP
"David Lozzi" <dlozzi@.nospam.nospam> wrote in message
news:u6smwZ$ZGHA.1196@.TK2MSFTNGP03.phx.gbl...
> Howdy,
> I just accidently wiped out a table that had some pretty important data in
> it. Can I restore it from the transaction log? Here's what I've tried so
> far
> and I get the errors as stated below. I did do "net pause mssqlserver"
> before running it.
> USE master
> RESTORE DATABASE cpts
> FROM DISK = 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\RPCS.mdf'
> WITH RECOVERY
> RESTORE LOG cpts
> FROM DISK = 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\Copy of
> RPCS.ldf'
> WITH RECOVERY, STOPAT = 'Apr 24, 2006 5:20 PM'
>
> Erros
> Server: Msg 3101, Level 16, State 2, Line 3
> Exclusive access could not be obtained because the database is in use.
> Server: Msg 3013, Level 16, State 1, Line 3
> RESTORE DATABASE is terminating abnormally.
> Server: Msg 3101, Level 16, State 2, Line 7
> Exclusive access could not be obtained because the database is in use.
> Server: Msg 3013, Level 16, State 1, Line 7
> RESTORE LOG is terminating abnormally.
> Thanks!!
> David Lozzi
>|||Seems you are trying to restore from the database files (mdf, ldf). That is
not how RESTORE work,
You restore from backup files (taken by the TSQL BACKUP command).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"David Lozzi" <dlozzi@.nospam.nospam> wrote in message news:u6smwZ$ZGHA.1196@.TK2MSFTNGP03.ph
x.gbl...
> Howdy,
> I just accidently wiped out a table that had some pretty important data in
> it. Can I restore it from the transaction log? Here's what I've tried so f
ar
> and I get the errors as stated below. I did do "net pause mssqlserver"
> before running it.
> USE master
> RESTORE DATABASE cpts
> FROM DISK = 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\RPCS.mdf'
> WITH RECOVERY
> RESTORE LOG cpts
> FROM DISK = 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\Copy of
> RPCS.ldf'
> WITH RECOVERY, STOPAT = 'Apr 24, 2006 5:20 PM'
>
> Erros
> Server: Msg 3101, Level 16, State 2, Line 3
> Exclusive access could not be obtained because the database is in use.
> Server: Msg 3013, Level 16, State 1, Line 3
> RESTORE DATABASE is terminating abnormally.
> Server: Msg 3101, Level 16, State 2, Line 7
> Exclusive access could not be obtained because the database is in use.
> Server: Msg 3013, Level 16, State 1, Line 7
> RESTORE LOG is terminating abnormally.
> Thanks!!
> David Lozzi
>|||Good catch, Tibor.
Hope this helps.
Dan Guzman
SQL Server MVP
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%235lJqxFaGHA.4292@.TK2MSFTNGP04.phx.gbl...
> Seems you are trying to restore from the database files (mdf, ldf). That
> is not how RESTORE work, You restore from backup files (taken by the TSQL
> BACKUP command).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "David Lozzi" <dlozzi@.nospam.nospam> wrote in message
> news:u6smwZ$ZGHA.1196@.TK2MSFTNGP03.phx.gbl...
>

Errors in log when running data-driven subscriptions

The following messages are displayed in one of the RS logs when running a
data-driven subscription:
ReportingServicesService!processing!820!12/17/2004-05:03:03:: e ERROR: There
is no data for the field at position 277.
ReportingServicesService!processing!820!12/17/2004-05:03:03:: e ERROR: There
is no data for the field at position 278.
ReportingServicesService!processing!820!12/17/2004-05:03:03:: e ERROR: There
is no data for the field at position 279.
What do they mean? What is the position referring to? The data-driven
subscription uses a query that selects a subset of the records in a table.
Thanks.I believe it is referring to the fields in the query. Does you query return
280 columns? How did you create the DD subscription, via Report Manager or
SOAP? If it was via soap, it is possible that your field list is not
identical to what is returned from the query. If you run the query through
PrepareQuery you should get an appropriate field listing.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"PD" <PD@.discussions.microsoft.com> wrote in message
news:E5E8B150-0891-4154-9C9B-7532FB911E7F@.microsoft.com...
> The following messages are displayed in one of the RS logs when running a
> data-driven subscription:
> ReportingServicesService!processing!820!12/17/2004-05:03:03:: e ERROR:
> There
> is no data for the field at position 277.
> ReportingServicesService!processing!820!12/17/2004-05:03:03:: e ERROR:
> There
> is no data for the field at position 278.
> ReportingServicesService!processing!820!12/17/2004-05:03:03:: e ERROR:
> There
> is no data for the field at position 279.
> What do they mean? What is the position referring to? The data-driven
> subscription uses a query that selects a subset of the records in a table.
> Thanks.|||The query only returns 1 column from a table with 4 columns total. I created
the subscription using the Report Manager.
"Daniel Reib [MSFT]" wrote:
> I believe it is referring to the fields in the query. Does you query return
> 280 columns? How did you create the DD subscription, via Report Manager or
> SOAP? If it was via soap, it is possible that your field list is not
> identical to what is returned from the query. If you run the query through
> PrepareQuery you should get an appropriate field listing.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "PD" <PD@.discussions.microsoft.com> wrote in message
> news:E5E8B150-0891-4154-9C9B-7532FB911E7F@.microsoft.com...
> > The following messages are displayed in one of the RS logs when running a
> > data-driven subscription:
> >
> > ReportingServicesService!processing!820!12/17/2004-05:03:03:: e ERROR:
> > There
> > is no data for the field at position 277.
> > ReportingServicesService!processing!820!12/17/2004-05:03:03:: e ERROR:
> > There
> > is no data for the field at position 278.
> > ReportingServicesService!processing!820!12/17/2004-05:03:03:: e ERROR:
> > There
> > is no data for the field at position 279.
> >
> > What do they mean? What is the position referring to? The data-driven
> > subscription uses a query that selects a subset of the records in a table.
> >
> > Thanks.
>
>|||Hmmm. Can you send a little more of the log file. Perhaps that will shed
some light.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"PD" <PD@.discussions.microsoft.com> wrote in message
news:1C6EA567-4DF7-40C1-8713-FCD68ABC32DF@.microsoft.com...
> The query only returns 1 column from a table with 4 columns total. I
> created
> the subscription using the Report Manager.
> "Daniel Reib [MSFT]" wrote:
>> I believe it is referring to the fields in the query. Does you query
>> return
>> 280 columns? How did you create the DD subscription, via Report Manager
>> or
>> SOAP? If it was via soap, it is possible that your field list is not
>> identical to what is returned from the query. If you run the query
>> through
>> PrepareQuery you should get an appropriate field listing.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "PD" <PD@.discussions.microsoft.com> wrote in message
>> news:E5E8B150-0891-4154-9C9B-7532FB911E7F@.microsoft.com...
>> > The following messages are displayed in one of the RS logs when running
>> > a
>> > data-driven subscription:
>> >
>> > ReportingServicesService!processing!820!12/17/2004-05:03:03:: e ERROR:
>> > There
>> > is no data for the field at position 277.
>> > ReportingServicesService!processing!820!12/17/2004-05:03:03:: e ERROR:
>> > There
>> > is no data for the field at position 278.
>> > ReportingServicesService!processing!820!12/17/2004-05:03:03:: e ERROR:
>> > There
>> > is no data for the field at position 279.
>> >
>> > What do they mean? What is the position referring to? The data-driven
>> > subscription uses a query that selects a subset of the records in a
>> > table.
>> >
>> > Thanks.
>>|||Daniel,
I have the same problem. The error occurs when I run as a scheduled report
... the report runs fine all other times.
Here is an excerpt from my log file. See the error message after RenderFirst.
aspnet_wp!library!504!12/20/2004-15:41:07:: i INFO: Call to GetPermissions:/
aspnet_wp!library!504!12/20/2004-15:41:07:: i INFO: Call to
GetSystemPermissions
aspnet_wp!library!4b4!12/20/2004-15:42:16:: i INFO: Call to GetPermissions:/
aspnet_wp!library!4b4!12/20/2004-15:42:16:: i INFO: Call to
GetSystemPermissions
aspnet_wp!library!504!12/20/2004-15:42:33:: i INFO: Call to
GetPermissions:/Dashboards
aspnet_wp!library!504!12/20/2004-15:42:33:: i INFO: Call to
GetSystemPermissions
aspnet_wp!library!4b4!12/20/2004-15:42:35:: i INFO: Call to
GetPermissions:/Dashboards/PatientVolumeActivity
aspnet_wp!library!4b4!12/20/2004-15:42:35:: i INFO: Call to
GetSystemPermissions
aspnet_wp!library!4b4!12/20/2004-15:42:36:: i INFO: Call to RenderFirst(
'/Dashboards/PatientVolumeActivity' )
aspnet_wp!processing!b18!12/20/2004-15:42:37:: e ERROR: There is no data for
the field at position 3.
aspnet_wp!library!4b4!12/20/2004-15:42:37:: i INFO: Initializing
EnableExecutionLogging to 'True' as specified in Server system properties.
aspnet_wp!webserver!4b4!12/20/2004-15:42:37:: i INFO: Processed report.
Report='/Dashboards/PatientVolumeActivity', Stream=''
aspnet_wp!chunks!4b4!12/20/2004-15:42:38:: i INFO: ###
GetReportChunk('C_3_S', 1), chunk was not found!
this=d27cd042-e1ce-45c5-bc6a-2211ddca2424
aspnet_wp!chunks!504!12/20/2004-15:42:38:: i INFO: ###
GetReportChunk('C_50_S', 1), chunk was not found!
this=d27cd042-e1ce-45c5-bc6a-2211ddca2424
aspnet_wp!webserver!4b4!12/20/2004-15:42:38:: i INFO: Processed report.
Report='/Dashboards/PatientVolumeActivity', Stream='C_3_S'
aspnet_wp!webserver!504!12/20/2004-15:42:38:: i INFO: Processed report.
Report='/Dashboards/PatientVolumeActivity', Stream='C_50_S'
aspnet_wp!chunks!504!12/20/2004-15:42:38:: i INFO: ###
GetReportChunk('C_111_S', 1), chunk was not found!
this=d27cd042-e1ce-45c5-bc6a-2211ddca2424
aspnet_wp!chunks!4b4!12/20/2004-15:42:38:: i INFO: ###
GetReportChunk('C_140_S', 1), chunk was not found!
this=d27cd042-e1ce-45c5-bc6a-2211ddca2424
aspnet_wp!webserver!504!12/20/2004-15:42:38:: i INFO: Processed report.
Report='/Dashboards/PatientVolumeActivity', Stream='C_111_S'
aspnet_wp!webserver!4b4!12/20/2004-15:42:38:: i INFO: Processed report.
Report='/Dashboards/PatientVolumeActivity', Stream='C_140_S'
aspnet_wp!library!504!12/20/2004-15:42:40:: i INFO: Call to
GetPermissions:/Dashboards/PatientVolumeActivity
aspnet_wp!library!504!12/20/2004-15:42:40:: i INFO: Call to
GetSystemPermissions
"Daniel Reib [MSFT]" wrote:
> Hmmm. Can you send a little more of the log file. Perhaps that will shed
> some light.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "PD" <PD@.discussions.microsoft.com> wrote in message
> news:1C6EA567-4DF7-40C1-8713-FCD68ABC32DF@.microsoft.com...
> > The query only returns 1 column from a table with 4 columns total. I
> > created
> > the subscription using the Report Manager.
> >
> > "Daniel Reib [MSFT]" wrote:
> >
> >> I believe it is referring to the fields in the query. Does you query
> >> return
> >> 280 columns? How did you create the DD subscription, via Report Manager
> >> or
> >> SOAP? If it was via soap, it is possible that your field list is not
> >> identical to what is returned from the query. If you run the query
> >> through
> >> PrepareQuery you should get an appropriate field listing.
> >>
> >> --
> >> -Daniel
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >>
> >> "PD" <PD@.discussions.microsoft.com> wrote in message
> >> news:E5E8B150-0891-4154-9C9B-7532FB911E7F@.microsoft.com...
> >> > The following messages are displayed in one of the RS logs when running
> >> > a
> >> > data-driven subscription:
> >> >
> >> > ReportingServicesService!processing!820!12/17/2004-05:03:03:: e ERROR:
> >> > There
> >> > is no data for the field at position 277.
> >> > ReportingServicesService!processing!820!12/17/2004-05:03:03:: e ERROR:
> >> > There
> >> > is no data for the field at position 278.
> >> > ReportingServicesService!processing!820!12/17/2004-05:03:03:: e ERROR:
> >> > There
> >> > is no data for the field at position 279.
> >> >
> >> > What do they mean? What is the position referring to? The data-driven
> >> > subscription uses a query that selects a subset of the records in a
> >> > table.
> >> >
> >> > Thanks.
> >>
> >>
> >>
>
>

Errors in log

The following are errors I found in one of my SQL Server Logs:
Error: 17207, Severity: 16, State: 1.
FCB::RemoveAlternateStreams: Operating system error (null) occurred while
creating or opening file 'C:\Program Files\Microsoft SQL
Server\MSSQL\data\master.mdf'. Diagnose and correct the operating system
error, and retry the operation.
Recovery is writing a checkpoint in database 'master' (1). This is an
informational message only. No user action is required.
CHECKDB for database 'master' finished without errors on 2007-06-12
14:09:11.613 (local time). This is an informational message only; no user
action is required.
I checked the security for master database file and it is ok. Any idea what
could cause this? thanks.
LijunOn Jun 12, 9:13 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> The following are errors I found in one of my SQL Server Logs:
> Error: 17207, Severity: 16, State: 1.
> FCB::RemoveAlternateStreams: Operating system error (null) occurred while
> creating or opening file 'C:\Program Files\Microsoft SQL
> Server\MSSQL\data\master.mdf'. Diagnose and correct the operating system
> error, and retry the operation.
> Recovery is writing a checkpoint in database 'master' (1). This is an
> informational message only. No user action is required.
> CHECKDB for database 'master' finished without errors on 2007-06-12
> 14:09:11.613 (local time). This is an informational message only; no user
> action is required.
> I checked the security for master database file and it is ok. Any idea what
> could cause this? thanks.
> Lijun
Hi
Does this error happen regularly?
Other applications accessing the file such as Anti-Virus software can
cause problems similar to this e.g.
https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=201223&SiteID=1
John|||Yes. I have to rebuild the master database to solve the problem.
Lijun
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1181719774.789471.92510@.o11g2000prd.googlegroups.com...
> On Jun 12, 9:13 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
>> The following are errors I found in one of my SQL Server Logs:
>> Error: 17207, Severity: 16, State: 1.
>> FCB::RemoveAlternateStreams: Operating system error (null) occurred while
>> creating or opening file 'C:\Program Files\Microsoft SQL
>> Server\MSSQL\data\master.mdf'. Diagnose and correct the operating system
>> error, and retry the operation.
>> Recovery is writing a checkpoint in database 'master' (1). This is an
>> informational message only. No user action is required.
>> CHECKDB for database 'master' finished without errors on 2007-06-12
>> 14:09:11.613 (local time). This is an informational message only; no user
>> action is required.
>> I checked the security for master database file and it is ok. Any idea
>> what
>> could cause this? thanks.
>> Lijun
> Hi
> Does this error happen regularly?
> Other applications accessing the file such as Anti-Virus software can
> cause problems similar to this e.g.
> https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=201223&SiteID=1
> John
>|||Hi Lijun
On Jun 13, 8:23 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> Yes. I have to rebuild the master database to solve the problem.
> Lijun
> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
> news:1181719774.789471.92510@.o11g2000prd.googlegroups.com...
That seems quite drastic as the message is only a warning and CHECKDB
returned no errors! Do you know what the cause was?
John|||No. I don't know what is the cause.
Lijun
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1181805578.143092.163530@.n15g2000prd.googlegroups.com...
> Hi Lijun
> On Jun 13, 8:23 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
>> Yes. I have to rebuild the master database to solve the problem.
>> Lijun
>> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
>> news:1181719774.789471.92510@.o11g2000prd.googlegroups.com...
> That seems quite drastic as the message is only a warning and CHECKDB
> returned no errors! Do you know what the cause was?
> John
>