Help : Table Corrupt

Can not truncate or drop a table.
DBCC CHECKTABLE on the table returns the following message:
"Table Corrupt: IAM page (1:25040) (object ID 38016033,
index ID 0) is out of the range of this database."
Our version is Microsoft SQL Server 7.00 - 7.00.623
Can this corrupt other tables?
Thanks.Here are the general recommendations for handling a suspect or corrupt
database:
0. Ensure you have a backup strategy that you can use to recover from
hardware failures (including corruption). I recommend performing both
database and log backup in most situations.
1. If you can run DBCC CHECKDB against the database: Search Books Online and
KB for the error numbers that CHECKDB gives you. There might be specific
info for that type of error.
2. Find out why this happened. Check eventlog, do HW diagnostics etc.;
search Books Online and KB for those errors. You don't want this to happen
again! If the database is suspect, the file might have been in use by for
instance an anti-virus program and restarting SQL Server might be all that
is needed - but you still want to read logs etc to find out what happened.
3. If there is a hardware problem, ensure the faulty hardware is replaced.
4. Backup the log. This assumes that log backup schedule is in place, of
course. If the database is suspect, then the NO_TRUNCATE option for the
RESTORE command must be used. Also, you might want to do a file backup of
the mdf and ldf files, for extra safety.
5. Restore is the best thing to do now. If you managed to backup log as per
step 4, then you will most probably have zero dataloss. You should restore
the latest clean database backup and the subsequent log backups including
the one taken in above step.
If the database isn't suspect, then DBCC with a REPAIR option might be a
secondary option but this will often result in loss of data. Additional
solutions, depending on the errors, may be to manually rebuild non-clustered
indexes, manually drop and reload a table if the data is static, and so on.
If the database is suspect, a secondary option can be to try to "un-suspect"
the database using sp_resetstatus. Read about it (books online, KB, google
etc). It might help but if the database is too damaged, it might just pop
back to suspect again. There's also something called "emergency mode" which
is a "panic" status you can set in order to try to get data out of a damaged
database. I think the name of that option speaks for itself. Again search
the net for info.
If you feel uncertain with above steps, I recommend letting MS hand-hold you
through the steps appropriate for your particular situation.
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"xeiger" <xeiger@.yahoo.es> wrote in message
news:baf601c3ecce$8df61a40$a001280a@.phx.gbl...
> Can not truncate or drop a table.
> DBCC CHECKTABLE on the table returns the following message:
> "Table Corrupt: IAM page (1:25040) (object ID 38016033,
> index ID 0) is out of the range of this database."
> Our version is Microsoft SQL Server 7.00 - 7.00.623
> Can this corrupt other tables?
> Thanks.

Help : Table Corrupt

Can not truncate or drop a table.
DBCC CHECKTABLE on the table returns the following message:
"Table Corrupt: IAM page (1:25040) (object ID 38016033,
index ID 0) is out of the range of this database."
Our version is Microsoft SQL Server 7.00 - 7.00.623
Can this corrupt other tables?
Thanks.Here are the general recommendations for handling a suspect or corrupt
database:
0. Ensure you have a backup strategy that you can use to recover from
hardware failures (including corruption). I recommend performing both
database and log backup in most situations.
1. If you can run DBCC CHECKDB against the database: Search Books Online and
KB for the error numbers that CHECKDB gives you. There might be specific
info for that type of error.
2. Find out why this happened. Check eventlog, do HW diagnostics etc.;
search Books Online and KB for those errors. You don't want this to happen
again! If the database is suspect, the file might have been in use by for
instance an anti-virus program and restarting SQL Server might be all that
is needed - but you still want to read logs etc to find out what happened.
3. If there is a hardware problem, ensure the faulty hardware is replaced.
4. Backup the log. This assumes that log backup schedule is in place, of
course. If the database is suspect, then the NO_TRUNCATE option for the
RESTORE command must be used. Also, you might want to do a file backup of
the mdf and ldf files, for extra safety.
5. Restore is the best thing to do now. If you managed to backup log as per
step 4, then you will most probably have zero dataloss. You should restore
the latest clean database backup and the subsequent log backups including
the one taken in above step.
If the database isn't suspect, then DBCC with a REPAIR option might be a
secondary option but this will often result in loss of data. Additional
solutions, depending on the errors, may be to manually rebuild non-clustered
indexes, manually drop and reload a table if the data is static, and so on.
If the database is suspect, a secondary option can be to try to "un-suspect"
the database using sp_resetstatus. Read about it (books online, KB, google
etc). It might help but if the database is too damaged, it might just pop
back to suspect again. There's also something called "emergency mode" which
is a "panic" status you can set in order to try to get data out of a damaged
database. I think the name of that option speaks for itself. Again search
the net for info.
If you feel uncertain with above steps, I recommend letting MS hand-hold you
through the steps appropriate for your particular situation.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"xeiger" <xeiger@.yahoo.es> wrote in message
news:baf601c3ecce$8df61a40$a001280a@.phx.gbl...
> Can not truncate or drop a table.
> DBCC CHECKTABLE on the table returns the following message:
> "Table Corrupt: IAM page (1:25040) (object ID 38016033,
> index ID 0) is out of the range of this database."
> Our version is Microsoft SQL Server 7.00 - 7.00.623
> Can this corrupt other tables?
> Thanks.

HELP - Error Message when running DBCC Showcontig with TableResults

Has anyone encountered the following error message when
running DBCC Showcontig with tableresults?
[Microsoft][ODBC SQL Server Driver]Unknown token received
from SQL Server
I am doing a dynamic DBCC on every table in my DB to
perform some analysis of indexes, however when I run the
full DB, I get this error. I printed the table.index for
each index prior to running the dbcc and when I take the
table and index and run independantly in ISQL, it executes
fine, but gives me a message about:
'DBCC execution completed. If DBCC printed error messages,
contact your system administrator.'
Which is not viable since it is a text string and not the
parameters of the TABLERESULTS table.
Anyone have a workaround or know what I can do to fix this?I'd start checking the database using CHECKDB. If that comes out clean, I'd say you've hit a bug
(check KB, be current and if that doesn't help open case with MS PSS).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Chris" <chris@.da-krewe.com> wrote in message news:066a01c391af$9183bca0$a101280a@.phx.gbl...
> Has anyone encountered the following error message when
> running DBCC Showcontig with tableresults?
> [Microsoft][ODBC SQL Server Driver]Unknown token received
> from SQL Server
> I am doing a dynamic DBCC on every table in my DB to
> perform some analysis of indexes, however when I run the
> full DB, I get this error. I printed the table.index for
> each index prior to running the dbcc and when I take the
> table and index and run independantly in ISQL, it executes
> fine, but gives me a message about:
> 'DBCC execution completed. If DBCC printed error messages,
> contact your system administrator.'
> Which is not viable since it is a text string and not the
> parameters of the TABLERESULTS table.
> Anyone have a workaround or know what I can do to fix this?

Help (DBCC SHOWCONTIG ( + @tablename + )

Hi everyone, I'm SO glad I found this site.
Ok, here's my problem...

I found this stored proc somewhere to help defrag some tables, well this one line is giving me the hardest time. First I was getting an error about using FAST ('FAST' is not a recognized option.), so I took that out.
Now I'm getting 'ALL_INDEXES' is not a recognized option.

Here's the line giving me the problems.
EXEC ('DBCC SHOWCONTIG (''' + @.tablename + ''') with TABLERESULTS, NO_INFOMSGS,ALL_INDEXES')

Any ideas?

Thank you!RE: Here's the line giving me the problems.
EXEC ('DBCC SHOWCONTIG (''' + @.tablename + ''') with TABLERESULTS, NO_INFOMSGS,ALL_INDEXES')

Note: Often the line where the error is 'reported' to be (in query analyzer, etc.) is not where it the issue actually is; frequently that is just where the query parser 'chokes' on it. The line you gave in isolation should work OK. Have you tried it seperatly to test it? For example try:

Use Pubs
GO

Declare @.tablename As NVarChar (256)
Select @.tablename = 'Authors'

Exec ('DBCC SHOWCONTIG (''' + @.tablename + ''') with TABLERESULTS, NO_INFOMSGS, ALL_INDEXES')|||That keyword is not valid. If you include the table id without the index id - all indexes will be processed.|||RE: That keyword is not valid. If you include the table id without the index id - all indexes will be processed.

I'm not sure I understand what you mean, if you mean All_Indexes; as far as I understand it will cause results for "all indexes" to be displayed. In this case for Pubs..authors?

Use Pubs
GO

Declare @.tablename As NVarChar (256)
Select @.tablename = 'Authors'

Exec ('DBCC SHOWCONTIG (''' + @.tablename + ''') with TABLERESULTS, NO_INFOMSGS, ALL_INDEXES')|||I needed to be more specific - ALL_INDEXES is not a valid keyword for sql server 7 - that is why criki is having the problem. Same reason why fast was not working.|||Originally posted by rnealejr
I needed to be more specific - ALL_INDEXES is not a valid keyword for sql server 7 - that is why criki is having the problem. Same reason why fast was not working.

I had assumed criki was on Sql Server 2k; also I thought Sql 2k returns esults for a clustered / pk index (if you leave out index ids...) I guess 7.0 returns results for all inexes if you leave out index ids?|||Whoa! You guys lost me.
I am on 2000. I found the code in help. I would assume FAST and ALL_INDEXES would be accurate. I just figured there's some setting I'm missing.

The full code is in SQL Server Books Online under DBCC SHOWCONTIG|||You say you are running SQL Server 2000, was this an install or an upgrade from SQL Server 7.0. If it was an upgrade your Compatibility Level for the database may still be set to SQL Server 7.

Run this to see the levels
select cmptlevel,name from master.dbo.sysdatabases
If a database comes back with a cmptlevel not equal to 80, then it is not at 2000 level.

You can set a databases Compatibility Level by running sp_dbcmptlevel. However this may have some effect on your stored procedures, so test.|||They're all 70. :-(
Most of my databases don't have stored procedures, luckily in this case.

What type of issues and is there anyway to determine this before running running sp_dbcmptlevel?|||The only difference between levels 70 and 80 is that several reserved keywords introduced in SQL Server 2000 are not supported in level 70.|||When you upgrade from 7 to 2000 the default compatibility is to 2000 (8) so I am surprised that your compatibility it still for 7. Anyway, the short answer to your question is yes. Check out the following ms articles:

ms article 1 (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_backcomp_02wj.asp)

ms article 2 (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_backcomp_5dx1.asp) - This one says version 6.5, but there is some important information in general and specifically to version 7.|||So sorry! I was told Sql 2K but it is in fact 7.0. (that's what I get for not checking myself)

Now, I guess, best thing to do is just rewrite the proc to include the correct fields in the table creation and insert.

I'll have to start a new thread!

Thanks!

HELP

Help Me
What Can I do... I have this error when i try DBCC CHECKDB. I try to do
REPAIR FAST, but it send me the same text (in spanish) :
Servidor: mensaje 1101, nivel 17, estado 10, línea 3
No se puede asignar una nueva página para la base de datos 'TEMPDB'. No hay
más páginas disponibles en el grupo de archivos DEFAULT. Puede crear espacio
si quita objetos, archivos adicionales o si permite que el archivo crezca.
Servidor: mensaje 8921, nivel 16, estado 1, línea 1
CHECKTABLE terminado. Detectado error al recopilar hechos. Posiblemente
falta espacio para tempdb o hay una tabla de sistema dañada. Consulte los
errores anteriores.
Resultados de DBCC para 'Ventas0503'.
CHECKDB ha encontrado 0 errores de asignación y 1 errores de consistencia no
asociados a ningún objeto determinado.
CHECKDB ha encontrado 0 errores de asignación y 1 errores de consistencia en
la base de datos 'Ventas0503'.
repair_fast es el nivel de reparación mínimo para los errores encontrados
por DBCC CHECKDB (Ventas0503 repair_fast).Perhaps you could provide the general idea of the error message for those of us in America that only speak English.
>--Original Message--
>Help Me
>What Can I do... I have this error when i try DBCC CHECKDB. I try to do
>REPAIR FAST, but it send me the same text (in spanish) :
>Servidor: mensaje 1101, nivel 17, estado 10, l=EDnea 3
>No se puede asignar una nueva p=E1gina para la base de datos 'TEMPDB'. No hay
>m=E1s p=E1ginas disponibles en el grupo de archivos DEFAULT. Puede crear espacio
>si quita objetos, archivos adicionales o si permite que el archivo crezca.
>Servidor: mensaje 8921, nivel 16, estado 1, l=EDnea 1
>CHECKTABLE terminado. Detectado error al recopilar hechos. Posiblemente
>falta espacio para tempdb o hay una tabla de sistema da=F1ada. Consulte los
>errores anteriores.
>Resultados de DBCC para 'Ventas0503'.
>CHECKDB ha encontrado 0 errores de asignaci=F3n y 1 errores de consistencia no
>asociados a ning=FAn objeto determinado.
>CHECKDB ha encontrado 0 errores de asignaci=F3n y 1 errores de consistencia en
>la base de datos 'Ventas0503'.
>repair_fast es el nivel de reparaci=F3n m=EDnimo para los errores encontrados
>por DBCC CHECKDB (Ventas0503 repair_fast).
>
>.
>|||Sorry... I will try to traduce you.
The msg 1101, level 17, status 10 and line 3 said:
It's not possible to assign a new page for TEMPDB database. There aren't
more available pages at the files group DEFAULT. You can create space if you
drop objects, extra files, or if you permit ttha the file grow.
Then The msg 8921, level 16, status 1, line 1 said:
Error detected. There isn't space for TEMPDB or there are a damage system
table. Consult the errors listed before.
Additionaly, I check TEMPDB and all is normal with it.
Help me please. Thanks in advance.
"chris" <anonymous@.discussions.microsoft.com> escribió en el mensaje
news:0c7301c3a552$84256390$a601280a@.phx.gbl...
Perhaps you could provide the general idea of the error
message for those of us in America that only speak English.
>--Original Message--
>Help Me
>What Can I do... I have this error when i try DBCC
CHECKDB. I try to do
>REPAIR FAST, but it send me the same text (in spanish) :
>Servidor: mensaje 1101, nivel 17, estado 10, línea 3
>No se puede asignar una nueva página para la base de
datos 'TEMPDB'. No hay
>más páginas disponibles en el grupo de archivos DEFAULT.
Puede crear espacio
>si quita objetos, archivos adicionales o si permite que
el archivo crezca.
>Servidor: mensaje 8921, nivel 16, estado 1, línea 1
>CHECKTABLE terminado. Detectado error al recopilar
hechos. Posiblemente
>falta espacio para tempdb o hay una tabla de sistema
dañada. Consulte los
>errores anteriores.
>Resultados de DBCC para 'Ventas0503'.
>CHECKDB ha encontrado 0 errores de asignación y 1 errores
de consistencia no
>asociados a ningún objeto determinado.
>CHECKDB ha encontrado 0 errores de asignación y 1 errores
de consistencia en
>la base de datos 'Ventas0503'.
>repair_fast es el nivel de reparación mínimo para los
errores encontrados
>por DBCC CHECKDB (Ventas0503 repair_fast).
>
>.
>|||I believe that CHECKDB nowadays need working space in tempdb. I recommend
that you expand the size of your tempdb. Btw, why do you want to run the
REPAIR_FAST option?
Also, check out below:
http://support.microsoft.com/default.aspx?scid=kb;en-us;305635
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Salvador De los Reyes" <sdlreyes@.hotmail.com> wrote in message
news:usIg7TVpDHA.1632@.TK2MSFTNGP10.phx.gbl...
> Sorry... I will try to traduce you.
> The msg 1101, level 17, status 10 and line 3 said:
> It's not possible to assign a new page for TEMPDB database. There aren't
> more available pages at the files group DEFAULT. You can create space if
you
> drop objects, extra files, or if you permit ttha the file grow.
> Then The msg 8921, level 16, status 1, line 1 said:
> Error detected. There isn't space for TEMPDB or there are a damage system
> table. Consult the errors listed before.
> Additionaly, I check TEMPDB and all is normal with it.
> Help me please. Thanks in advance.
> "chris" <anonymous@.discussions.microsoft.com> escribió en el mensaje
> news:0c7301c3a552$84256390$a601280a@.phx.gbl...
> Perhaps you could provide the general idea of the error
> message for those of us in America that only speak English.
> >--Original Message--
> >Help Me
> >
> >What Can I do... I have this error when i try DBCC
> CHECKDB. I try to do
> >REPAIR FAST, but it send me the same text (in spanish) :
> >
> >Servidor: mensaje 1101, nivel 17, estado 10, línea 3
> >No se puede asignar una nueva página para la base de
> datos 'TEMPDB'. No hay
> >más páginas disponibles en el grupo de archivos DEFAULT.
> Puede crear espacio
> >si quita objetos, archivos adicionales o si permite que
> el archivo crezca.
> >Servidor: mensaje 8921, nivel 16, estado 1, línea 1
> >CHECKTABLE terminado. Detectado error al recopilar
> hechos. Posiblemente
> >falta espacio para tempdb o hay una tabla de sistema
> dañada. Consulte los
> >errores anteriores.
> >Resultados de DBCC para 'Ventas0503'.
> >CHECKDB ha encontrado 0 errores de asignación y 1 errores
> de consistencia no
> >asociados a ningún objeto determinado.
> >CHECKDB ha encontrado 0 errores de asignación y 1 errores
> de consistencia en
> >la base de datos 'Ventas0503'.
> >repair_fast es el nivel de reparación mínimo para los
> errores encontrados
> >por DBCC CHECKDB (Ventas0503 repair_fast).
> >
> >
> >.
> >
>|||You can also run DBCC CHECKDB with the ESTIMATEONLY option to see if you
have enough tempdb space or not.
--
Andrew J. Kelly
SQL Server MVP
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:eHAeGfVpDHA.964@.TK2MSFTNGP10.phx.gbl...
> I believe that CHECKDB nowadays need working space in tempdb. I recommend
> that you expand the size of your tempdb. Btw, why do you want to run the
> REPAIR_FAST option?
> Also, check out below:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;305635
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Salvador De los Reyes" <sdlreyes@.hotmail.com> wrote in message
> news:usIg7TVpDHA.1632@.TK2MSFTNGP10.phx.gbl...
> >
> > Sorry... I will try to traduce you.
> >
> > The msg 1101, level 17, status 10 and line 3 said:
> > It's not possible to assign a new page for TEMPDB database. There aren't
> > more available pages at the files group DEFAULT. You can create space if
> you
> > drop objects, extra files, or if you permit ttha the file grow.
> >
> > Then The msg 8921, level 16, status 1, line 1 said:
> > Error detected. There isn't space for TEMPDB or there are a damage
system
> > table. Consult the errors listed before.
> >
> > Additionaly, I check TEMPDB and all is normal with it.
> >
> > Help me please. Thanks in advance.
> >
> > "chris" <anonymous@.discussions.microsoft.com> escribió en el mensaje
> > news:0c7301c3a552$84256390$a601280a@.phx.gbl...
> > Perhaps you could provide the general idea of the error
> > message for those of us in America that only speak English.
> >
> > >--Original Message--
> > >Help Me
> > >
> > >What Can I do... I have this error when i try DBCC
> > CHECKDB. I try to do
> > >REPAIR FAST, but it send me the same text (in spanish) :
> > >
> > >Servidor: mensaje 1101, nivel 17, estado 10, línea 3
> > >No se puede asignar una nueva página para la base de
> > datos 'TEMPDB'. No hay
> > >más páginas disponibles en el grupo de archivos DEFAULT.
> > Puede crear espacio
> > >si quita objetos, archivos adicionales o si permite que
> > el archivo crezca.
> > >Servidor: mensaje 8921, nivel 16, estado 1, línea 1
> > >CHECKTABLE terminado. Detectado error al recopilar
> > hechos. Posiblemente
> > >falta espacio para tempdb o hay una tabla de sistema
> > dañada. Consulte los
> > >errores anteriores.
> > >Resultados de DBCC para 'Ventas0503'.
> > >CHECKDB ha encontrado 0 errores de asignación y 1 errores
> > de consistencia no
> > >asociados a ningún objeto determinado.
> > >CHECKDB ha encontrado 0 errores de asignación y 1 errores
> > de consistencia en
> > >la base de datos 'Ventas0503'.
> > >repair_fast es el nivel de reparación mínimo para los
> > errores encontrados
> > >por DBCC CHECKDB (Ventas0503 repair_fast).
> > >
> > >
> > >.
> > >
> >
> >
>|||Good one, Andrew. I totally forgot about that... :-)
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eRMYD9VpDHA.392@.TK2MSFTNGP11.phx.gbl...
> You can also run DBCC CHECKDB with the ESTIMATEONLY option to see if you
> have enough tempdb space or not.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "Tibor Karaszi"
<tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
> wrote in message news:eHAeGfVpDHA.964@.TK2MSFTNGP10.phx.gbl...
> > I believe that CHECKDB nowadays need working space in tempdb. I
recommend
> > that you expand the size of your tempdb. Btw, why do you want to run the
> > REPAIR_FAST option?
> >
> > Also, check out below:
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;305635
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > Archive at:
> >
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> > "Salvador De los Reyes" <sdlreyes@.hotmail.com> wrote in message
> > news:usIg7TVpDHA.1632@.TK2MSFTNGP10.phx.gbl...
> > >
> > > Sorry... I will try to traduce you.
> > >
> > > The msg 1101, level 17, status 10 and line 3 said:
> > > It's not possible to assign a new page for TEMPDB database. There
aren't
> > > more available pages at the files group DEFAULT. You can create space
if
> > you
> > > drop objects, extra files, or if you permit ttha the file grow.
> > >
> > > Then The msg 8921, level 16, status 1, line 1 said:
> > > Error detected. There isn't space for TEMPDB or there are a damage
> system
> > > table. Consult the errors listed before.
> > >
> > > Additionaly, I check TEMPDB and all is normal with it.
> > >
> > > Help me please. Thanks in advance.
> > >
> > > "chris" <anonymous@.discussions.microsoft.com> escribió en el mensaje
> > > news:0c7301c3a552$84256390$a601280a@.phx.gbl...
> > > Perhaps you could provide the general idea of the error
> > > message for those of us in America that only speak English.
> > >
> > > >--Original Message--
> > > >Help Me
> > > >
> > > >What Can I do... I have this error when i try DBCC
> > > CHECKDB. I try to do
> > > >REPAIR FAST, but it send me the same text (in spanish) :
> > > >
> > > >Servidor: mensaje 1101, nivel 17, estado 10, línea 3
> > > >No se puede asignar una nueva página para la base de
> > > datos 'TEMPDB'. No hay
> > > >más páginas disponibles en el grupo de archivos DEFAULT.
> > > Puede crear espacio
> > > >si quita objetos, archivos adicionales o si permite que
> > > el archivo crezca.
> > > >Servidor: mensaje 8921, nivel 16, estado 1, línea 1
> > > >CHECKTABLE terminado. Detectado error al recopilar
> > > hechos. Posiblemente
> > > >falta espacio para tempdb o hay una tabla de sistema
> > > dañada. Consulte los
> > > >errores anteriores.
> > > >Resultados de DBCC para 'Ventas0503'.
> > > >CHECKDB ha encontrado 0 errores de asignación y 1 errores
> > > de consistencia no
> > > >asociados a ningún objeto determinado.
> > > >CHECKDB ha encontrado 0 errores de asignación y 1 errores
> > > de consistencia en
> > > >la base de datos 'Ventas0503'.
> > > >repair_fast es el nivel de reparación mínimo para los
> > > errores encontrados
> > > >por DBCC CHECKDB (Ventas0503 repair_fast).
> > > >
> > > >
> > > >.
> > > >
> > >
> > >
> >
> >
>|||How is that ?
Dbcc checkdb ('NameDB',ESTIMATEONLY) '
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> escribió en el mensaje
news:eRMYD9VpDHA.392@.TK2MSFTNGP11.phx.gbl...
> You can also run DBCC CHECKDB with the ESTIMATEONLY option to see if you
> have enough tempdb space or not.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "Tibor Karaszi"
<tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
> wrote in message news:eHAeGfVpDHA.964@.TK2MSFTNGP10.phx.gbl...
> > I believe that CHECKDB nowadays need working space in tempdb. I
recommend
> > that you expand the size of your tempdb. Btw, why do you want to run the
> > REPAIR_FAST option?
> >
> > Also, check out below:
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;305635
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > Archive at:
> >
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> > "Salvador De los Reyes" <sdlreyes@.hotmail.com> wrote in message
> > news:usIg7TVpDHA.1632@.TK2MSFTNGP10.phx.gbl...
> > >
> > > Sorry... I will try to traduce you.
> > >
> > > The msg 1101, level 17, status 10 and line 3 said:
> > > It's not possible to assign a new page for TEMPDB database. There
aren't
> > > more available pages at the files group DEFAULT. You can create space
if
> > you
> > > drop objects, extra files, or if you permit ttha the file grow.
> > >
> > > Then The msg 8921, level 16, status 1, line 1 said:
> > > Error detected. There isn't space for TEMPDB or there are a damage
> system
> > > table. Consult the errors listed before.
> > >
> > > Additionaly, I check TEMPDB and all is normal with it.
> > >
> > > Help me please. Thanks in advance.
> > >
> > > "chris" <anonymous@.discussions.microsoft.com> escribió en el mensaje
> > > news:0c7301c3a552$84256390$a601280a@.phx.gbl...
> > > Perhaps you could provide the general idea of the error
> > > message for those of us in America that only speak English.
> > >
> > > >--Original Message--
> > > >Help Me
> > > >
> > > >What Can I do... I have this error when i try DBCC
> > > CHECKDB. I try to do
> > > >REPAIR FAST, but it send me the same text (in spanish) :
> > > >
> > > >Servidor: mensaje 1101, nivel 17, estado 10, línea 3
> > > >No se puede asignar una nueva página para la base de
> > > datos 'TEMPDB'. No hay
> > > >más páginas disponibles en el grupo de archivos DEFAULT.
> > > Puede crear espacio
> > > >si quita objetos, archivos adicionales o si permite que
> > > el archivo crezca.
> > > >Servidor: mensaje 8921, nivel 16, estado 1, línea 1
> > > >CHECKTABLE terminado. Detectado error al recopilar
> > > hechos. Posiblemente
> > > >falta espacio para tempdb o hay una tabla de sistema
> > > dañada. Consulte los
> > > >errores anteriores.
> > > >Resultados de DBCC para 'Ventas0503'.
> > > >CHECKDB ha encontrado 0 errores de asignación y 1 errores
> > > de consistencia no
> > > >asociados a ningún objeto determinado.
> > > >CHECKDB ha encontrado 0 errores de asignación y 1 errores
> > > de consistencia en
> > > >la base de datos 'Ventas0503'.
> > > >repair_fast es el nivel de reparación mínimo para los
> > > errores encontrados
> > > >por DBCC CHECKDB (Ventas0503 repair_fast).
> > > >
> > > >
> > > >.
> > > >
> > >
> > >
> >
> >
>|||Because is suggested by DBCC CHECKDB.
Thks
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
escribió en el mensaje news:eHAeGfVpDHA.964@.TK2MSFTNGP10.phx.gbl...
> I believe that CHECKDB nowadays need working space in tempdb. I recommend
> that you expand the size of your tempdb. Btw, why do you want to run the
> REPAIR_FAST option?
> Also, check out below:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;305635
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Salvador De los Reyes" <sdlreyes@.hotmail.com> wrote in message
> news:usIg7TVpDHA.1632@.TK2MSFTNGP10.phx.gbl...
> >
> > Sorry... I will try to traduce you.
> >
> > The msg 1101, level 17, status 10 and line 3 said:
> > It's not possible to assign a new page for TEMPDB database. There aren't
> > more available pages at the files group DEFAULT. You can create space if
> you
> > drop objects, extra files, or if you permit ttha the file grow.
> >
> > Then The msg 8921, level 16, status 1, line 1 said:
> > Error detected. There isn't space for TEMPDB or there are a damage
system
> > table. Consult the errors listed before.
> >
> > Additionaly, I check TEMPDB and all is normal with it.
> >
> > Help me please. Thanks in advance.
> >
> > "chris" <anonymous@.discussions.microsoft.com> escribió en el mensaje
> > news:0c7301c3a552$84256390$a601280a@.phx.gbl...
> > Perhaps you could provide the general idea of the error
> > message for those of us in America that only speak English.
> >
> > >--Original Message--
> > >Help Me
> > >
> > >What Can I do... I have this error when i try DBCC
> > CHECKDB. I try to do
> > >REPAIR FAST, but it send me the same text (in spanish) :
> > >
> > >Servidor: mensaje 1101, nivel 17, estado 10, línea 3
> > >No se puede asignar una nueva página para la base de
> > datos 'TEMPDB'. No hay
> > >más páginas disponibles en el grupo de archivos DEFAULT.
> > Puede crear espacio
> > >si quita objetos, archivos adicionales o si permite que
> > el archivo crezca.
> > >Servidor: mensaje 8921, nivel 16, estado 1, línea 1
> > >CHECKTABLE terminado. Detectado error al recopilar
> > hechos. Posiblemente
> > >falta espacio para tempdb o hay una tabla de sistema
> > dañada. Consulte los
> > >errores anteriores.
> > >Resultados de DBCC para 'Ventas0503'.
> > >CHECKDB ha encontrado 0 errores de asignación y 1 errores
> > de consistencia no
> > >asociados a ningún objeto determinado.
> > >CHECKDB ha encontrado 0 errores de asignación y 1 errores
> > de consistencia en
> > >la base de datos 'Ventas0503'.
> > >repair_fast es el nivel de reparación mínimo para los
> > errores encontrados
> > >por DBCC CHECKDB (Ventas0503 repair_fast).
> > >
> > >
> > >.
> > >
> >
> >
>|||BooksOnLine has the syntax for all the options:
Dbcc checkdb ('NameDB') WITH ESTIMATEONLY
Andrew J. Kelly
SQL Server MVP
"Salvador De los Reyes" <sdlreyes@.hotmail.com> wrote in message
news:e14sAEYpDHA.976@.tk2msftngp13.phx.gbl...
> How is that ?
> Dbcc checkdb ('NameDB',ESTIMATEONLY) '
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> escribió en el mensaje
> news:eRMYD9VpDHA.392@.TK2MSFTNGP11.phx.gbl...
> > You can also run DBCC CHECKDB with the ESTIMATEONLY option to see if you
> > have enough tempdb space or not.
> >
> > --
> >
> > Andrew J. Kelly
> > SQL Server MVP
> >
> >
> > "Tibor Karaszi"
> <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
> > wrote in message news:eHAeGfVpDHA.964@.TK2MSFTNGP10.phx.gbl...
> > > I believe that CHECKDB nowadays need working space in tempdb. I
> recommend
> > > that you expand the size of your tempdb. Btw, why do you want to run
the
> > > REPAIR_FAST option?
> > >
> > > Also, check out below:
> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;305635
> > >
> > > --
> > > Tibor Karaszi, SQL Server MVP
> > > Archive at:
> > >
> >
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
> > >
> > >
> > > "Salvador De los Reyes" <sdlreyes@.hotmail.com> wrote in message
> > > news:usIg7TVpDHA.1632@.TK2MSFTNGP10.phx.gbl...
> > > >
> > > > Sorry... I will try to traduce you.
> > > >
> > > > The msg 1101, level 17, status 10 and line 3 said:
> > > > It's not possible to assign a new page for TEMPDB database. There
> aren't
> > > > more available pages at the files group DEFAULT. You can create
space
> if
> > > you
> > > > drop objects, extra files, or if you permit ttha the file grow.
> > > >
> > > > Then The msg 8921, level 16, status 1, line 1 said:
> > > > Error detected. There isn't space for TEMPDB or there are a damage
> > system
> > > > table. Consult the errors listed before.
> > > >
> > > > Additionaly, I check TEMPDB and all is normal with it.
> > > >
> > > > Help me please. Thanks in advance.
> > > >
> > > > "chris" <anonymous@.discussions.microsoft.com> escribió en el mensaje
> > > > news:0c7301c3a552$84256390$a601280a@.phx.gbl...
> > > > Perhaps you could provide the general idea of the error
> > > > message for those of us in America that only speak English.
> > > >
> > > > >--Original Message--
> > > > >Help Me
> > > > >
> > > > >What Can I do... I have this error when i try DBCC
> > > > CHECKDB. I try to do
> > > > >REPAIR FAST, but it send me the same text (in spanish) :
> > > > >
> > > > >Servidor: mensaje 1101, nivel 17, estado 10, línea 3
> > > > >No se puede asignar una nueva página para la base de
> > > > datos 'TEMPDB'. No hay
> > > > >más páginas disponibles en el grupo de archivos DEFAULT.
> > > > Puede crear espacio
> > > > >si quita objetos, archivos adicionales o si permite que
> > > > el archivo crezca.
> > > > >Servidor: mensaje 8921, nivel 16, estado 1, línea 1
> > > > >CHECKTABLE terminado. Detectado error al recopilar
> > > > hechos. Posiblemente
> > > > >falta espacio para tempdb o hay una tabla de sistema
> > > > dañada. Consulte los
> > > > >errores anteriores.
> > > > >Resultados de DBCC para 'Ventas0503'.
> > > > >CHECKDB ha encontrado 0 errores de asignación y 1 errores
> > > > de consistencia no
> > > > >asociados a ningún objeto determinado.
> > > > >CHECKDB ha encontrado 0 errores de asignación y 1 errores
> > > > de consistencia en
> > > > >la base de datos 'Ventas0503'.
> > > > >repair_fast es el nivel de reparación mínimo para los
> > > > errores encontrados
> > > > >por DBCC CHECKDB (Ventas0503 repair_fast).
> > > > >
> > > > >
> > > > >.
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||I always recommend that you do a log backup and then restore the database
including all subsequent log backups into a new database name in these
cases. Chances are that you get zero data loss. Then you can try the repair.
If that doesn't cut it, you have that other database as an option.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Salvador De los Reyes" <sdlreyes@.hotmail.com> wrote in message
news:%23u0bnFYpDHA.1072@.TK2MSFTNGP09.phx.gbl...
> Because is suggested by DBCC CHECKDB.
> Thks
> "Tibor Karaszi"
<tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
> escribió en el mensaje news:eHAeGfVpDHA.964@.TK2MSFTNGP10.phx.gbl...
> > I believe that CHECKDB nowadays need working space in tempdb. I
recommend
> > that you expand the size of your tempdb. Btw, why do you want to run the
> > REPAIR_FAST option?
> >
> > Also, check out below:
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;305635
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > Archive at:
> >
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> > "Salvador De los Reyes" <sdlreyes@.hotmail.com> wrote in message
> > news:usIg7TVpDHA.1632@.TK2MSFTNGP10.phx.gbl...
> > >
> > > Sorry... I will try to traduce you.
> > >
> > > The msg 1101, level 17, status 10 and line 3 said:
> > > It's not possible to assign a new page for TEMPDB database. There
aren't
> > > more available pages at the files group DEFAULT. You can create space
if
> > you
> > > drop objects, extra files, or if you permit ttha the file grow.
> > >
> > > Then The msg 8921, level 16, status 1, line 1 said:
> > > Error detected. There isn't space for TEMPDB or there are a damage
> system
> > > table. Consult the errors listed before.
> > >
> > > Additionaly, I check TEMPDB and all is normal with it.
> > >
> > > Help me please. Thanks in advance.
> > >
> > > "chris" <anonymous@.discussions.microsoft.com> escribió en el mensaje
> > > news:0c7301c3a552$84256390$a601280a@.phx.gbl...
> > > Perhaps you could provide the general idea of the error
> > > message for those of us in America that only speak English.
> > >
> > > >--Original Message--
> > > >Help Me
> > > >
> > > >What Can I do... I have this error when i try DBCC
> > > CHECKDB. I try to do
> > > >REPAIR FAST, but it send me the same text (in spanish) :
> > > >
> > > >Servidor: mensaje 1101, nivel 17, estado 10, línea 3
> > > >No se puede asignar una nueva página para la base de
> > > datos 'TEMPDB'. No hay
> > > >más páginas disponibles en el grupo de archivos DEFAULT.
> > > Puede crear espacio
> > > >si quita objetos, archivos adicionales o si permite que
> > > el archivo crezca.
> > > >Servidor: mensaje 8921, nivel 16, estado 1, línea 1
> > > >CHECKTABLE terminado. Detectado error al recopilar
> > > hechos. Posiblemente
> > > >falta espacio para tempdb o hay una tabla de sistema
> > > dañada. Consulte los
> > > >errores anteriores.
> > > >Resultados de DBCC para 'Ventas0503'.
> > > >CHECKDB ha encontrado 0 errores de asignación y 1 errores
> > > de consistencia no
> > > >asociados a ningún objeto determinado.
> > > >CHECKDB ha encontrado 0 errores de asignación y 1 errores
> > > de consistencia en
> > > >la base de datos 'Ventas0503'.
> > > >repair_fast es el nivel de reparación mínimo para los
> > > errores encontrados
> > > >por DBCC CHECKDB (Ventas0503 repair_fast).
> > > >
> > > >
> > > >.
> > > >
> > >
> > >
> >
> >
>