Hi,

I believe I'm running into a backward compatibility issue with the sqlserver
05 Enterprise edition. I restored a database from sqlserver 2000 to my new
sqlserver 2005. Both of my .net project and Access gets time-out errors
(running remotely) when they try to access to a table that I have modified
via query analyzer in sqlserver 2005. I had no problem reading the table via
those clients before I touched its data, so it looks like modifying data in
those table creating an incompatiblity issue.

Has anybody run into similar situation before? Thank you very much in
advance for your help!

Never mind. I had a transaction failed to commit or rollback because of a
fatal error and so my subsequence data modification statements would just
lock up the tables.

"Zen" <zen@nononospam.com> wrote in message
news:eKrY0y3fGHA.5092@TK2MSFTNGP04.phx.gbl...
> Hi,
>
> I believe I'm running into a backward compatibility issue with the
> sqlserver 05 Enterprise edition. I restored a database from sqlserver 2000
> to my new sqlserver 2005. Both of my .net project and Access gets
> time-out errors (running remotely) when they try to access to a table that
> I have modified via query analyzer in sqlserver 2005. I had no problem
> reading the table via those clients before I touched its data, so it looks
> like modifying data in those table creating an incompatiblity issue.
>
> Has anybody run into similar situation before? Thank you very much in
> advance for your help!
>