Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1105
  • Last Modified:

Error after attaching a database

I am using MS SQL 2000 Server
I had attached a database (.mdf) of size of around 1GB and after attaching when i query a table using SELECT statement i am displayed around 6550 rows and then it displays an error as given below :


Server: Msg 3624, Level 20, State 1, Line 1
 
Location:      q:\SPHINX\NTDBMS\storeng\drs\include\record.inl:1447
Expression:      m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
SPID:           54
Process ID:      784

Connection Broken
0
viswa20
Asked:
viswa20
1 Solution
 
lozzamooreCommented:
Which front end tool are you using to run the Select statement from?
Cheers,
0
 
Dr_DatabaseCommented:
The described problem may be, that the clustered index of the table is corrupted after the failed add column attempt. A clustered index may be corrupted if all of the following conditions are met:

You tried to add a column to an existing table and in the same transaction you added a foreign key reference from the new column to a column that is a unique clustered or unique nonclustered index key on the same table.

The add column failed and the transaction was rolled back.

After the transaction failed and was rolled back, an INSERT statement to the same table may result in an error message similar to one you mentioned.

To work around this problem you can either:
Drop, and then re-create the index.
-or-
Use this statement to re-create the corrupted index:
CREATE CLUSTERED INDEX...WITH DROP_EXISTING

Hope this helps.

Regards,
Dr. Database
0
 
Scott PletcherSenior DBACommented:
Is the database you attached the same version and release level (including Service Pack) as the 2000 server?  If it's not, problems may arise because of internal differences in the format of .MDFs.

If, for example, it's a SQL 7.0 database, a backup and restore -- rather than an sp_attach -- should work.  If you can't make a backup from the original .mdf source, you may need to install a SQL Server instance that's at the proper release level, attach the .mdf, do a backup, then restore that backup to your new 2000 instance.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
moduloCommented:
Dear: Dr_Database

I've rejected your proposed answer as Experts Exchange holds an experiment to work without the answer button.

See:        http://www.experts-exchange.com/jsp/communityNews.jsp
Paragraph: Site Update for Wednesday, November 06, 2002

By this rejection the Asker will be notified by mail and hopefully he will take his responsibility to finalize the question or post an additional comment.
The Asker sees a button beside every post which says "Accept This Comment As Answer" (including rejected answers) -- so if he/she thinks yours is the best, you'll be awarded the points and the grade.

Thanks !

modulo

Community Support Moderator
Experts Exchange
0
 
CleanupPingCommented:
viswa20:
This old question needs to be finalized -- accept an answer, split points, or get a refund.  For information on your options, please click here-> http:/help/closing.jsp#1 
EXPERTS:
Post your closing recommendations!  No comment means you don't care.
0
 
moduloCommented:
PAQ'd and points removed

modulo

Community Support Moderator
Experts Exchange
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now