July 21, 2008 at 12:39 pm
Hello,
We are experiencing the following error when attempting to SELECT from a text column on SQL Server 7:
"Server: Msg 7102, Level 20, State 99, Line 1
SQL Server Internal Error. Text manager cannot continue with current statement.
Connection Broken"
The database @@VERSION is:
"Microsoft SQL Server 7.00 - 7.00.1141 (Intel X86) Sep 5 2003 17:48:54 Copyright (c) 1988-2002 Microsoft Corporation Enterprise Edition on Windows NT 4.0 (Build 1381: Service Pack 6) "
Searching the web, in general, has yielded similar issues described by others, but not with a context similar enough for us to solve our problem.
My feedback to my client has been to ultimately upgrade SQL Server 7 to a version supported by Microsoft (with the understanding that Microsoft no longer supports SQL Server 7). Until that is possible, my client would like to retrieve the data and save it if off somewhere - if possible. That is where this posting comes to play. I was asked to seek help with this (when backup retrieval is not an option).
Here is what I have been able to do:
- DBCC Check db /table : neither report errors
- Backup SQL 7 database (no errors reported)
- Restore as new database to existing 2000 server (no errors reported)
- DBCC Check db /table : neither report errors on SQL 2000
- Selecting from the table still gives errors
- copy table using SELECT * INTO (ironically, no errors)
- SELECT from the new table (text column has only one CHAR(13), but no errors reported). I.e., the data is lost in the copy.
I'd really appreciate any feedback regarding how to potentially retrieve the inaccessible data.
Kind Regards
July 23, 2008 at 7:48 am
July 23, 2008 at 8:44 am
Thank you Terry for looking into this. We have seen that article. While the error message is almost identical, our context seems a little different, and the article claims this problem to have been resolved with Service Pack 2. After executing @@Version and comparing the output (7.00.1141) with Microsoft's Release Table at http://support.microsoft.com/kb/321185, it looks like we have a hotfix version greater than SP4. Also, neither of the workarounds applied for us.
Thanks,
Steve
July 23, 2008 at 9:20 am
I'm guessing you've done your research but here are a couple of additional links. The only other thing I can think of is placing a call to PSS. Might be money well spent.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=748077&SiteID=1
http://www.sqlservercentral.com/Forums/Topic141479-145-1.aspx#bm145115
http://education.sqlfarms.com/education/ShowPost.aspx?PostID=189
-- You can't be late until you show up.
July 23, 2008 at 10:45 am
I really appreciate your help Terry. I'll check those links out. My colleagues here have informed me that MS no longer supports SQL 7. (I originally wanted to call MS too, and I agree with you - well worth the money spent.)
I'll keep you posted with any outcomes, and please don't hesitate to share any other ideas you may think of.
Kind Regards,
Steve
July 23, 2008 at 12:48 pm
Forgot about Microsoft discontining support. I've been off of 7.0 for quite some time, though still on 2000....What I've read on several links is it's not corruption and you've proved that out based on your original post. Any hopes of going to 2000 or 2005 anytime soon? Is this causing a production situtation?
-- You can't be late until you show up.
July 23, 2008 at 1:17 pm
This is in production. Fortunately, the column in question, while important, is less critical than others (so I am told). There are efforts in place to move to SQL 2000, but I think that will be several months down the road...
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply