July 4, 2008 at 12:03 am
Hmmm.
Check the source database please, make sure that you have either torn page detection or checksum (open the database properties, go to options and scroll down to the section "recovery")
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 5, 2008 at 12:23 am
Hi,
I am executing a stored procedure and i encountered the following error :
Server: Msg 3624, Level 20, State 1, Line 1
Location: recbase.cpp:1375
Expression: m_offBeginVar < m_SizeRec
SPID: 63
Process ID: 688
Connection Broken
After zeroing in the SP I came across a particulary query which was generating the above error the rest part of the SP was fine. Further zeroing in led me to a table , when i executed a simple selection query on the table it generated the same error I just created a new table by the same name copied the data and VOILA! every thing worked just fine. I think this error is related to the consistency of data. Just wanted to share my experience.
Regards,
:)Avaneesh Bajoria
July 12, 2008 at 6:10 am
Dear Ben,
I have faced similar issues with one of my client's DB where Service pack wasn't installed.
so i suggest you to update the latest service pack to resolve this issue permanently.
SQL SERVER 2000 SERVICE PACK 3 or 4 will solve the issue.
Regards,
Mayuresh
MayurArt
July 12, 2008 at 6:35 am
Mayuresh (7/12/2008)
SQL SERVER 2000 SERVICE PACK 3 or 4 will solve the issue.
Since he's running SQL 2005, I seriously doubt it.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 13, 2008 at 9:42 am
I am running Sql 2000 sp3. I found the problem, unfortunately I have no idea how it happened. When I had some time to mess around on the production system it was obvious the physical dick had become corrupt. There was a multitude of storage and disk related errors in windows event log.
I ran check disk at reboot to fix that, which ended up rendering the server unbootable after fixing the disk errors. Had to call MS, they got the server back up and running after several hours but SQl Server service would no longer start. My options were to open a ticket with the SQL Server support group or renistall sql. Had to reinstall SQL and restore all DB's from backups. Not a pleasant day at all.
Thanks everyone!
Ben
July 13, 2008 at 11:55 pm
Ben Blum (7/13/2008)
I am running Sql 2000 sp3. I found the problem, unfortunately I have no idea how it happened. When I had some time to mess around on the production system it was obvious the physical dick had become corrupt. There was a multitude of storage and disk related errors in windows event log.
May I suggest replacing that drive? Prior experience has taught me that disk errors have a nasty habit of reoccuring.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 14, 2008 at 7:33 am
Ben Blum (7/13/2008)
it was obvious the physical dick had become corrupt.
Sounds PAINFUL! - Sorry, a little (very little) Monday morning humor to kick off the week....:Whistling:
-- You can't be late until you show up.
Viewing 7 posts - 16 through 21 (of 21 total)
You must be logged in to reply to this topic. Login to reply