Can't recalculate db size / can't rebuild index 
Author Message
 Can't recalculate db size / can't rebuild index

Hey everybody,
I'm fairly new to SQL server and I'm in a bit of a pickle.  Any comments /
suggestions would be greatly appreciated.

My log filled up.  I was able to expand the device and then the log db and
truncate the log.  I then tried to recalculate the db size and I got error
#2541.  I did a dbcc checkdb and a newalloc - I found one table that was
corrupt.  Since it is a temp table I dropped it and recreated it.  I then
ran newalloc and saw no errors.  I tried to recalculate the db size and
still got error#2541.  I then decided to try to rebuild all of the indexes
on the table mentioned in the 2541 error.  All of them worked fine execpt
one - when I hit rebuild, then execute now - I got an error "index "fname"
already exists".  The index appears to be working (judging by the speed  of
first name serches through our Access 2.0 front end).  I'm at a total loss
as to what to do.  Please advise.

Dave Mills
ABMP
Systems Administrator

--
Dave Mills
Associated Bodywork & Massage Professionals
Systems Administrator

www.abmp.com



Sun, 31 Dec 2000 03:00:00 GMT
 Can't recalculate db size / can't rebuild index

Quote:
>Hey everybody,
>I'm fairly new to SQL server and I'm in a bit of a pickle.  Any comments /
>suggestions would be greatly appreciated.

>My log filled up.  I was able to expand the device and then the log db and
>truncate the log.  I then tried to recalculate the db size and I got error
>#2541.  I did a dbcc checkdb and a newalloc - I found one table that was
>corrupt.  Since it is a temp table I dropped it and recreated it.  I then
>ran newalloc and saw no errors.  I tried to recalculate the db size and
>still got error#2541.  I then decided to try to rebuild all of the indexes
>on the table mentioned in the 2541 error.  All of them worked fine execpt
>one - when I hit rebuild, then execute now - I got an error "index "fname"
>already exists".  The index appears to be working (judging by the speed  of
>first name serches through our Access 2.0 front end).  I'm at a total loss
>as to what to do.  Please advise.

>Dave Mills
>ABMP
>Systems Administrator

>--
>Dave Mills
>Associated Bodywork & Massage Professionals
>Systems Administrator

>www.abmp.com

First, next time your log fills up, do this to trucate it:

1) Truncate the log (In Enterprise manager, right click on your db, select
EDIT, and click on TRUCATE)
2) Run DBCC CHECKTABLE(syslogs)
3) Repeat step one.

Your log file should be back to around 100% free.

Secondly, I'd just drop your offending index and then recreate.

John



Mon, 01 Jan 2001 03:00:00 GMT
 Can't recalculate db size / can't rebuild index
Thanks for the reply, ---  I paid the $200 to talk to microsoft and got it
fixed.

I couldn't drop the index (from the EM anyway)

Thanks

--
Dave Mills
Associated Bodywork & Massage Professionals
Systems Administrator

www.abmp.com


Quote:
>>Hey everybody,
>>I'm fairly new to SQL server and I'm in a bit of a pickle.  Any comments /
>>suggestions would be greatly appreciated.

>>My log filled up.  I was able to expand the device and then the log db and
>>truncate the log.  I then tried to recalculate the db size and I got error
>>#2541.  I did a dbcc checkdb and a newalloc - I found one table that was
>>corrupt.  Since it is a temp table I dropped it and recreated it.  I then
>>ran newalloc and saw no errors.  I tried to recalculate the db size and
>>still got error#2541.  I then decided to try to rebuild all of the indexes
>>on the table mentioned in the 2541 error.  All of them worked fine execpt
>>one - when I hit rebuild, then execute now - I got an error "index "fname"
>>already exists".  The index appears to be working (judging by the speed
of
>>first name serches through our Access 2.0 front end).  I'm at a total loss
>>as to what to do.  Please advise.

>>Dave Mills
>>ABMP
>>Systems Administrator

>>--
>>Dave Mills
>>Associated Bodywork & Massage Professionals
>>Systems Administrator

>>www.abmp.com

>First, next time your log fills up, do this to trucate it:

>1) Truncate the log (In Enterprise manager, right click on your db, select
>EDIT, and click on TRUCATE)
>2) Run DBCC CHECKTABLE(syslogs)
>3) Repeat step one.

>Your log file should be back to around 100% free.

>Secondly, I'd just drop your offending index and then recreate.

>John



Mon, 01 Jan 2001 03:00:00 GMT
 
 [ 3 post ] 

 Relevant Pages 

1. if you will promise Allahdad's swamp against cans, it will angrily depart the unit

2. Anyone know of some canned (cheap or free) DB performance testing software

3. canned code to get db on web quickly via perl or

4. MDX : Canned Report or OLAP

5. Cans access2.0 engine access btrieve files?

6. bcp canned app

7. Switching from inhouse to canned package.

8. Canned PARADOX scripts?

9. Running a 'canned' Access Report from VB5

10. [SQL] Re: why the DB file size does not reduce when 'delete'the data

11. Dump size doesn't accord with the Data size of DB

12. Rebuilding index's on a database


 
Powered by phpBB® Forum Software