> On Apr 17, 1:20 pm, Bobby <bob***@blueyonder.co.uk> wrote:
>
> > A bit more information:
>
> > If I run a select on the table in SQL Query Analyzer, it hangs
> > everytime on record 15,936, so I guess that this does point to a data
> > corruption. But I'm still not sure why, or how I can fix it. Any
> > ideas?
>
> > Thanks
>
> > Colin
>
> see  in Books online for  DBCC CHECKTABLE

> On 17 Apr, 09:23, M A Srinivas <masri***@gmail.com> wrote:
>
> > On Apr 17, 1:20 pm, Bobby <bob***@blueyonder.co.uk> wrote:
>
> > > A bit more information:
>
> > > If I run a select on the table in SQL Query Analyzer, it hangs
> > > everytime on record 15,936, so I guess that this does point to a data
> > > corruption. But I'm still not sure why, or how I can fix it. Any
> > > ideas?
>
> > > Thanks
>
> > > Colin
>
> > see  in Books online for  DBCC CHECKTABLE
>
> Thanks
> When I run DBCC CHECKTABLE ('Timesheets') I get the following result:
>
> DBCC results for 'Timesheet - Item'.
> There are 17643 rows in 401 pages for object 'Timesheet - Item'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
>
> I can't see any errors. Where would it display the errors if there
> were any?
>
> Colin

"Bobby" <bob***@blueyonder.co.uk> wrote in message
news:1176795190.212707.170450@y5g2000hsa.googlegroups.com...
> Hi
> I've arrived in work this morning to find that my normally smooth
> running database is apparently "down". In reality, this means that I
> have one table, called "Timebookings", which has a problem.
>
> I use SQL Server as BE for and Access FE. When Access tries to use the
> table "Timebookings", it returns an ODBC timeout error. If I go into
> enterprise manager, I can open the table with apparently no problems,
> but if I try to go to the last record, or put an order by into  the
> SQL, or run a view which uses the table, I also get an ODBC timeout
> error. However, I can scroll through the table to the last record with
> no apparent problems. There are 18,000 records in the table, but as
> far as I can see, there is no data corruption. All other tables that I
> have checked seem fine.
>
> The exact message I get from Enterprise Manager is "[Microsoft][ODBC
> SQL Server Driver] Timout expired".
>
> My application has worked fine, 24/7,  for at least three months with
> no previous problems and nothing has changed that I am aware of in the
> past three weeks.
>
> Anybody got any suggestions as to what the cause of this might be, and
> how I might resolve it? Is there a repair table feature in SQL which I
> could use to try to correct the problem?
>
> Any suggestions would be very much appreciated,
>
> Thanks a lot
>
> Colin
>

"Tibor Karaszi" wrote:

> Are you absolutely certain that there's no blocking?
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
>
> "Bobby" <bob***@blueyonder.co.uk> wrote in message
> news:1176795190.212707.170450@y5g2000hsa.googlegroups.com...
> > Hi
> > I've arrived in work this morning to find that my normally smooth
> > running database is apparently "down". In reality, this means that I
> > have one table, called "Timebookings", which has a problem.
> >
> > I use SQL Server as BE for and Access FE. When Access tries to use the
> > table "Timebookings", it returns an ODBC timeout error. If I go into
> > enterprise manager, I can open the table with apparently no problems,
> > but if I try to go to the last record, or put an order by into  the
> > SQL, or run a view which uses the table, I also get an ODBC timeout
> > error. However, I can scroll through the table to the last record with
> > no apparent problems. There are 18,000 records in the table, but as
> > far as I can see, there is no data corruption. All other tables that I
> > have checked seem fine.
> >
> > The exact message I get from Enterprise Manager is "[Microsoft][ODBC
> > SQL Server Driver] Timout expired".
> >
> > My application has worked fine, 24/7,  for at least three months with
> > no previous problems and nothing has changed that I am aware of in the
> > past three weeks.
> >
> > Anybody got any suggestions as to what the cause of this might be, and
> > how I might resolve it? Is there a repair table feature in SQL which I
> > could use to try to correct the problem?
> >
> > Any suggestions would be very much appreciated,
> >
> > Thanks a lot
> >
> > Colin
> >
>
>
>