I am not certain, but I think that sql server will have stopped reponding
because it is:
a) Out of locks
or
b) The transaction log is full
To test b) edit the database under Enterprise manager. Ensure that the
transaction log has enoughj free space. If not you can press 'truncate',
however this usually does not work and you have to run 'dbcc checkdb(<your
db name>) through the query tool. Microsoft sucks !
To test a) see if you can run a query through enterprise manager after the
timeout occurs.
Paul
>>I have a database that consists of several tables, I've been able to
>>upsize all but one from Access97 to SQLServer using the upsizintg wizard.
>>The one that won't upsize contains about 30, 000 records. I've tried to
>>export to a ODBC database but I get a "ODBC driver Timeout expired #0"
>>error.
>>Can anyone tell me how to configure SQLServer or Access to eliminate the
>>timeout error and let the computer get back to exporting that table? Or
>>maybe a better way, I can't make heads or tales out of
>>these books yet...
>>Brian,
>I'd recommend exporting the table structure only. Make sure all your
>indexes and datatypes were transferred correctly, then you can append
>the data manually from Access. In your query, just increase the ODBC
>timeout in the query's properties. The Upsizing wizard is nice, but it
>doesn't do to well with large tables, or with appending the data, in
>my experience.
>Cheers,
>Anders
by