error index data base

Hi all,
I'm Jose and first of all excuse my english:
I have many problems with "Plan de mantenimiento de SQL" often when the
"Plan de mantenimiento" begin, have an errors during the reindex how:
Reconstruyendo los ?ndices de la tabla 'ws_Albaranes_Lineas'
[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624: [Microsoft][ODBC SQL
Server Driver][SQL Server]
[Microsoft][ODBC SQL Server Driver][SQL Server]Location: page.cpp:2831
Expression: spaceContig >= Align (spaceNeeded)
SPID: 54
Process ID: 1284
then marked how suspicous and can repair automatically, but when erros like
that occur for 4 or 5 times the database can't repair automatically and the
client lost data.
W2K SP4 and SQL SP3
Thanks a lot
OK, I understand a little 'Spanglish'. If I read correctly, you have chosen
the 'Repair minor problems Automatically' option in your Maintenance plans
("Plan de mantenimiento de SQL" ). The repair tried and failed and marked
the database suspect.
First, this repair automatically option a bad idea and I think it should not
be in the product. I never check this option. I want to know if there is a
problem so I can schedule a fix during non-peak times. I also want to know
so I can find what is causing the error.
The good news is you may be OK. the ws_indexes are actually statistics and
do not directly impact the data. Look at 'Resetting Suspect Status' in BOL
(Books On-Line). This may let you extract your data and recreate the
database.
This KB Article may help if nothing else works.
INF: Bypass (Emergency) Mode and DUMP TRANSACTION WITH NO_LOG
http://support.microsoft.com/default...b;en-us;165918
Good Luck.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
news:7592A326-4D93-4439-8BAB-1E95056C4809@.microsoft.com...
> Hi all,
> I'm Jose and first of all excuse my english:
> I have many problems with "Plan de mantenimiento de SQL" often when the
> "Plan de mantenimiento" begin, have an errors during the reindex how:
> Reconstruyendo los ndices de la tabla 'ws_Albaranes_Lineas'
> [Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]
> [Microsoft][ODBC SQL Server Driver][SQL Server]Location: page.cpp:2831
> Expression: spaceContig >= Align (spaceNeeded)
> SPID: 54
> Process ID: 1284
> then marked how suspicous and can repair automatically, but when erros
like
> that occur for 4 or 5 times the database can't repair automatically and
the
> client lost data.
> W2K SP4 and SQL SP3
> Thanks a lot
>
|||Hi again:
If I undestand, the correct option is: no marked the option "Repair minor
problems Automatically" but when the maintenance plans fail, always fail
during the reindex, The question is: Why reindex fail? For example the last
error that I wrote you:[vbcol=seagreen]
> SQL
Do you think I needn't reindex database?
"Geoff N. Hiten" wrote:

> OK, I understand a little 'Spanglish'. If I read correctly, you have chosen
> the 'Repair minor problems Automatically' option in your Maintenance plans
> ("Plan de mantenimiento de SQL" ). The repair tried and failed and marked
> the database suspect.
> First, this repair automatically option a bad idea and I think it should not
> be in the product. I never check this option. I want to know if there is a
> problem so I can schedule a fix during non-peak times. I also want to know
> so I can find what is causing the error.
> The good news is you may be OK. the ws_indexes are actually statistics and
> do not directly impact the data. Look at 'Resetting Suspect Status' in BOL
> (Books On-Line). This may let you extract your data and recreate the
> database.
> This KB Article may help if nothing else works.
> INF: Bypass (Emergency) Mode and DUMP TRANSACTION WITH NO_LOG
> http://support.microsoft.com/default...b;en-us;165918
> Good Luck.
>
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
> news:7592A326-4D93-4439-8BAB-1E95056C4809@.microsoft.com...
> SQL
> like
> the
>
>
|||I understand. It failed during a reindex. Reindexing is a good thing.
Continue to reindex.
Make sure your database has enough free space to reindex. Do not
auto-shrink the database. Manually add the space rather than relying on
auto-grow. Run DBCC CHECKDB to make sure your database is error free. You
may have to run further DBCC commands to fix it. Always make sure you have
a backup before attempting repairs.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
news:2E29E2B7-0A30-4CFD-937F-CCAABEDDBDB0@.microsoft.com...
> Hi again:
> If I undestand, the correct option is: no marked the option "Repair minor
> problems Automatically" but when the maintenance plans fail, always fail
> during the reindex, The question is: Why reindex fail? For example the
last[vbcol=seagreen]
> error that I wrote you:
[Microsoft][ODBC[vbcol=seagreen]
> Do you think I needn't reindex database?
> "Geoff N. Hiten" wrote:
chosen[vbcol=seagreen]
plans[vbcol=seagreen]
marked[vbcol=seagreen]
not[vbcol=seagreen]
is a[vbcol=seagreen]
know[vbcol=seagreen]
and[vbcol=seagreen]
BOL[vbcol=seagreen]
the[vbcol=seagreen]
[Microsoft][ODBC[vbcol=seagreen]
and[vbcol=seagreen]