My company has 5 SQL Servers, their configurations are : SQL Server 7.0 +
Service Pack 3.
But I could not do DBCC DBREINDEX on one of them and got the following error
:
DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
The error was :
Server: Msg 1105, Level 17, State 2, Line 1
Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
because the
'PRIMARY' filegroup is full.
Index (ID = 1) is being rebuilt.
Index (ID = 3) is being rebuilt.
Index (ID = 4) is being rebuilt.
But I don't think the error came from insufficient hard disk space because I
could execute the same command successfully on another machine that has even
less free hard disk space.
Can anybodies help me ?
Sometimes autogrow doesn't grow fast enough. The only way I know to handle this is to pre-allocate storage.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"cpchan" <cpchaney@.netvigator.com> wrote in message news:c97flr$rtl1@.imsp212.netvigator.com...
> My company has 5 SQL Servers, their configurations are : SQL Server 7.0 +
> Service Pack 3.
> But I could not do DBCC DBREINDEX on one of them and got the following error
> :
> DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
> The error was :
> Server: Msg 1105, Level 17, State 2, Line 1
> Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
> because the
> 'PRIMARY' filegroup is full.
> Index (ID = 1) is being rebuilt.
> Index (ID = 3) is being rebuilt.
> Index (ID = 4) is being rebuilt.
> But I don't think the error came from insufficient hard disk space because I
> could execute the same command successfully on another machine that has even
> less free hard disk space.
> Can anybodies help me ?
>
>
>
Showing posts with label dbcc. Show all posts
Showing posts with label dbcc. Show all posts
Monday, March 19, 2012
Could not Re-index !
My company has 5 SQL Servers, their configurations are : SQL Server 7.0 +
Service Pack 3.
But I could not do DBCC DBREINDEX on one of them and got the following error
:
DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
The error was :
Server: Msg 1105, Level 17, State 2, Line 1
Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
because the
'PRIMARY' filegroup is full.
Index (ID = 1) is being rebuilt.
Index (ID = 3) is being rebuilt.
Index (ID = 4) is being rebuilt.
But I don't think the error came from insufficient hard disk space because I
could execute the same command successfully on another machine that has even
less free hard disk space.
Can anybodies help me ?
Have you checked the settings of you data / log files to see if they have
reached there max size ?
J
"cpchan" <cpchaney@.netvigator.com> wrote in message
news:c9c7sj$j5r1618@.imsp212.netvigator.com...
> My company has 5 SQL Servers, their configurations are : SQL Server 7.0 +
> Service Pack 3.
> But I could not do DBCC DBREINDEX on one of them and got the following
error
> :
> DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
> The error was :
> Server: Msg 1105, Level 17, State 2, Line 1
> Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
> because the
> 'PRIMARY' filegroup is full.
> Index (ID = 1) is being rebuilt.
> Index (ID = 3) is being rebuilt.
> Index (ID = 4) is being rebuilt.
> But I don't think the error came from insufficient hard disk space because
I
> could execute the same command successfully on another machine that has
even
> less free hard disk space.
> Can anybodies help me ?
>
Service Pack 3.
But I could not do DBCC DBREINDEX on one of them and got the following error
:
DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
The error was :
Server: Msg 1105, Level 17, State 2, Line 1
Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
because the
'PRIMARY' filegroup is full.
Index (ID = 1) is being rebuilt.
Index (ID = 3) is being rebuilt.
Index (ID = 4) is being rebuilt.
But I don't think the error came from insufficient hard disk space because I
could execute the same command successfully on another machine that has even
less free hard disk space.
Can anybodies help me ?
Have you checked the settings of you data / log files to see if they have
reached there max size ?
J
"cpchan" <cpchaney@.netvigator.com> wrote in message
news:c9c7sj$j5r1618@.imsp212.netvigator.com...
> My company has 5 SQL Servers, their configurations are : SQL Server 7.0 +
> Service Pack 3.
> But I could not do DBCC DBREINDEX on one of them and got the following
error
> :
> DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
> The error was :
> Server: Msg 1105, Level 17, State 2, Line 1
> Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
> because the
> 'PRIMARY' filegroup is full.
> Index (ID = 1) is being rebuilt.
> Index (ID = 3) is being rebuilt.
> Index (ID = 4) is being rebuilt.
> But I don't think the error came from insufficient hard disk space because
I
> could execute the same command successfully on another machine that has
even
> less free hard disk space.
> Can anybodies help me ?
>
Could not Re-index !
My company has 5 SQL Servers, their configurations are : SQL Server 7.0 +
Service Pack 3.
But I could not do DBCC DBREINDEX on one of them and got the following error
:
DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
The error was :
Server: Msg 1105, Level 17, State 2, Line 1
Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
because the
'PRIMARY' filegroup is full.
Index (ID = 1) is being rebuilt.
Index (ID = 3) is being rebuilt.
Index (ID = 4) is being rebuilt.
But I don't think the error came from insufficient hard disk space because I
could execute the same command successfully on another machine that has even
less free hard disk space.
Can anybodies help me ?Sometimes autogrow doesn't grow fast enough. The only way I know to handle t
his is to pre-allocate storage.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"cpchan" <cpchaney@.netvigator.com> wrote in message news:c97flr$rtl1@.imsp212.netvigator.com.
.
> My company has 5 SQL Servers, their configurations are : SQL Server 7.0 +
> Service Pack 3.
> But I could not do DBCC DBREINDEX on one of them and got the following err
or
> :
> DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
> The error was :
> Server: Msg 1105, Level 17, State 2, Line 1
> Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
> because the
> 'PRIMARY' filegroup is full.
> Index (ID = 1) is being rebuilt.
> Index (ID = 3) is being rebuilt.
> Index (ID = 4) is being rebuilt.
> But I don't think the error came from insufficient hard disk space because
I
> could execute the same command successfully on another machine that has ev
en
> less free hard disk space.
> Can anybodies help me ?
>
>
>
Service Pack 3.
But I could not do DBCC DBREINDEX on one of them and got the following error
:
DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
The error was :
Server: Msg 1105, Level 17, State 2, Line 1
Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
because the
'PRIMARY' filegroup is full.
Index (ID = 1) is being rebuilt.
Index (ID = 3) is being rebuilt.
Index (ID = 4) is being rebuilt.
But I don't think the error came from insufficient hard disk space because I
could execute the same command successfully on another machine that has even
less free hard disk space.
Can anybodies help me ?Sometimes autogrow doesn't grow fast enough. The only way I know to handle t
his is to pre-allocate storage.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"cpchan" <cpchaney@.netvigator.com> wrote in message news:c97flr$rtl1@.imsp212.netvigator.com.
.
> My company has 5 SQL Servers, their configurations are : SQL Server 7.0 +
> Service Pack 3.
> But I could not do DBCC DBREINDEX on one of them and got the following err
or
> :
> DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
> The error was :
> Server: Msg 1105, Level 17, State 2, Line 1
> Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
> because the
> 'PRIMARY' filegroup is full.
> Index (ID = 1) is being rebuilt.
> Index (ID = 3) is being rebuilt.
> Index (ID = 4) is being rebuilt.
> But I don't think the error came from insufficient hard disk space because
I
> could execute the same command successfully on another machine that has ev
en
> less free hard disk space.
> Can anybodies help me ?
>
>
>
Could not Re-index !
My company has 5 SQL Servers, their configurations are : SQL Server 7.0 +
Service Pack 3.
But I could not do DBCC DBREINDEX on one of them and got the following error
:
DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
The error was :
Server: Msg 1105, Level 17, State 2, Line 1
Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
because the
'PRIMARY' filegroup is full.
Index (ID = 1) is being rebuilt.
Index (ID = 3) is being rebuilt.
Index (ID = 4) is being rebuilt.
But I don't think the error came from insufficient hard disk space because I
could execute the same command successfully on another machine that has even
less free hard disk space.
Can anybodies help me ?Have you checked the settings of you data / log files to see if they have
reached there max size ?
J
"cpchan" <cpchaney@.netvigator.com> wrote in message
news:c9c7sj$j5r1618@.imsp212.netvigator.com...
> My company has 5 SQL Servers, their configurations are : SQL Server 7.0 +
> Service Pack 3.
> But I could not do DBCC DBREINDEX on one of them and got the following
error
> :
> DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
> The error was :
> Server: Msg 1105, Level 17, State 2, Line 1
> Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
> because the
> 'PRIMARY' filegroup is full.
> Index (ID = 1) is being rebuilt.
> Index (ID = 3) is being rebuilt.
> Index (ID = 4) is being rebuilt.
> But I don't think the error came from insufficient hard disk space because
I
> could execute the same command successfully on another machine that has
even
> less free hard disk space.
> Can anybodies help me ?
>
Service Pack 3.
But I could not do DBCC DBREINDEX on one of them and got the following error
:
DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
The error was :
Server: Msg 1105, Level 17, State 2, Line 1
Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
because the
'PRIMARY' filegroup is full.
Index (ID = 1) is being rebuilt.
Index (ID = 3) is being rebuilt.
Index (ID = 4) is being rebuilt.
But I don't think the error came from insufficient hard disk space because I
could execute the same command successfully on another machine that has even
less free hard disk space.
Can anybodies help me ?Have you checked the settings of you data / log files to see if they have
reached there max size ?
J
"cpchan" <cpchaney@.netvigator.com> wrote in message
news:c9c7sj$j5r1618@.imsp212.netvigator.com...
> My company has 5 SQL Servers, their configurations are : SQL Server 7.0 +
> Service Pack 3.
> But I could not do DBCC DBREINDEX on one of them and got the following
error
> :
> DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
> The error was :
> Server: Msg 1105, Level 17, State 2, Line 1
> Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
> because the
> 'PRIMARY' filegroup is full.
> Index (ID = 1) is being rebuilt.
> Index (ID = 3) is being rebuilt.
> Index (ID = 4) is being rebuilt.
> But I don't think the error came from insufficient hard disk space because
I
> could execute the same command successfully on another machine that has
even
> less free hard disk space.
> Can anybodies help me ?
>
Thursday, March 8, 2012
could not find table error
Using SS2000 SP4.
When I run DBCC SHOWCONTIG (ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES I
get an error "Server: Msg 2501, Level 16, State 45, Line 1
Could not find a table or object named 'ActionsNeeded'. Check sysobjects."
All objects in the database are owned by "memsym". If I try "DBCC SHOWCONTIG
(memsym.ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES" I get this error -
"Server: Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near '.'."
I have a script that checks index fragmentation and it uses the above
command. I get the same error on all tables in the database. Any idea why and
how to fix it?
The tables do exist and I can select from them.
Thanks,
--
Dan D.> All objects in the database are owned by "memsym". If I try "DBCC
> SHOWCONTIG
> (memsym.ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES" I get this error -
> "Server: Msg 170, Level 15, State 1, Line 1
> Line 1: Incorrect syntax near '.'."
Try enclosing the object name in quotes:
DBCC SHOWCONTIG ('memsym.ActionsNeeded')
WITH TABLERESULTS, ALL_INDEXES
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:AEC3EE22-C7D7-4E81-A29D-36C5B698B241@.microsoft.com...
> Using SS2000 SP4.
> When I run DBCC SHOWCONTIG (ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES
> I
> get an error "Server: Msg 2501, Level 16, State 45, Line 1
> Could not find a table or object named 'ActionsNeeded'. Check sysobjects."
> All objects in the database are owned by "memsym". If I try "DBCC
> SHOWCONTIG
> (memsym.ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES" I get this error -
> "Server: Msg 170, Level 15, State 1, Line 1
> Line 1: Incorrect syntax near '.'."
> I have a script that checks index fragmentation and it uses the above
> command. I get the same error on all tables in the database. Any idea why
> and
> how to fix it?
> The tables do exist and I can select from them.
> Thanks,
> --
> Dan D.|||I guess I wasn't thinking this morning. That was too easy.
Thanks,
--
Dan D.
"Dan Guzman" wrote:
> > All objects in the database are owned by "memsym". If I try "DBCC
> > SHOWCONTIG
> > (memsym.ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES" I get this error -
> > "Server: Msg 170, Level 15, State 1, Line 1
> > Line 1: Incorrect syntax near '.'."
> Try enclosing the object name in quotes:
> DBCC SHOWCONTIG ('memsym.ActionsNeeded')
> WITH TABLERESULTS, ALL_INDEXES
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:AEC3EE22-C7D7-4E81-A29D-36C5B698B241@.microsoft.com...
> > Using SS2000 SP4.
> >
> > When I run DBCC SHOWCONTIG (ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES
> > I
> > get an error "Server: Msg 2501, Level 16, State 45, Line 1
> > Could not find a table or object named 'ActionsNeeded'. Check sysobjects."
> >
> > All objects in the database are owned by "memsym". If I try "DBCC
> > SHOWCONTIG
> > (memsym.ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES" I get this error -
> > "Server: Msg 170, Level 15, State 1, Line 1
> > Line 1: Incorrect syntax near '.'."
> >
> > I have a script that checks index fragmentation and it uses the above
> > command. I get the same error on all tables in the database. Any idea why
> > and
> > how to fix it?
> > The tables do exist and I can select from them.
> >
> > Thanks,
> > --
> > Dan D.
>
When I run DBCC SHOWCONTIG (ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES I
get an error "Server: Msg 2501, Level 16, State 45, Line 1
Could not find a table or object named 'ActionsNeeded'. Check sysobjects."
All objects in the database are owned by "memsym". If I try "DBCC SHOWCONTIG
(memsym.ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES" I get this error -
"Server: Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near '.'."
I have a script that checks index fragmentation and it uses the above
command. I get the same error on all tables in the database. Any idea why and
how to fix it?
The tables do exist and I can select from them.
Thanks,
--
Dan D.> All objects in the database are owned by "memsym". If I try "DBCC
> SHOWCONTIG
> (memsym.ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES" I get this error -
> "Server: Msg 170, Level 15, State 1, Line 1
> Line 1: Incorrect syntax near '.'."
Try enclosing the object name in quotes:
DBCC SHOWCONTIG ('memsym.ActionsNeeded')
WITH TABLERESULTS, ALL_INDEXES
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:AEC3EE22-C7D7-4E81-A29D-36C5B698B241@.microsoft.com...
> Using SS2000 SP4.
> When I run DBCC SHOWCONTIG (ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES
> I
> get an error "Server: Msg 2501, Level 16, State 45, Line 1
> Could not find a table or object named 'ActionsNeeded'. Check sysobjects."
> All objects in the database are owned by "memsym". If I try "DBCC
> SHOWCONTIG
> (memsym.ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES" I get this error -
> "Server: Msg 170, Level 15, State 1, Line 1
> Line 1: Incorrect syntax near '.'."
> I have a script that checks index fragmentation and it uses the above
> command. I get the same error on all tables in the database. Any idea why
> and
> how to fix it?
> The tables do exist and I can select from them.
> Thanks,
> --
> Dan D.|||I guess I wasn't thinking this morning. That was too easy.
Thanks,
--
Dan D.
"Dan Guzman" wrote:
> > All objects in the database are owned by "memsym". If I try "DBCC
> > SHOWCONTIG
> > (memsym.ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES" I get this error -
> > "Server: Msg 170, Level 15, State 1, Line 1
> > Line 1: Incorrect syntax near '.'."
> Try enclosing the object name in quotes:
> DBCC SHOWCONTIG ('memsym.ActionsNeeded')
> WITH TABLERESULTS, ALL_INDEXES
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:AEC3EE22-C7D7-4E81-A29D-36C5B698B241@.microsoft.com...
> > Using SS2000 SP4.
> >
> > When I run DBCC SHOWCONTIG (ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES
> > I
> > get an error "Server: Msg 2501, Level 16, State 45, Line 1
> > Could not find a table or object named 'ActionsNeeded'. Check sysobjects."
> >
> > All objects in the database are owned by "memsym". If I try "DBCC
> > SHOWCONTIG
> > (memsym.ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES" I get this error -
> > "Server: Msg 170, Level 15, State 1, Line 1
> > Line 1: Incorrect syntax near '.'."
> >
> > I have a script that checks index fragmentation and it uses the above
> > command. I get the same error on all tables in the database. Any idea why
> > and
> > how to fix it?
> > The tables do exist and I can select from them.
> >
> > Thanks,
> > --
> > Dan D.
>
Tuesday, February 14, 2012
Corrupted sysindexes
After running the command dbcc checkdb, which is part of a weekly job the following returned
CHECKDB found 1 allocation errors and 957 consistency errors in table 'sysindexes' (object ID 2).
Any ideas on how to fixed this sysindexes table.
I've run dbcc updateusage, dbbc reindex on all tables, dbbc checkdb
Considering it is sysindexes, my guess you are in for a restore. If that isn't convenient, opening a case with
MS is probably a good idea (but chances are that they don't have better options either). General
recommendations for corrupt or suspect databases: http://www.karaszi.com/sqlserver/inf...suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Stephen" <stephen.hoye@.tabq.com.au> wrote in message
news:89575553-91E2-459B-B6CD-0709E5C79463@.microsoft.com...
> After running the command dbcc checkdb, which is part of a weekly job the following returned
> CHECKDB found 1 allocation errors and 957 consistency errors in table 'sysindexes' (object ID 2).
> Any ideas on how to fixed this sysindexes table.
> I've run dbcc updateusage, dbbc reindex on all tables, dbbc checkdb
>
|||I'm going to create a DTS package and move the database over to anthor DB.
Then I'l rename them. We do have back up, but the problem was picked up after I long weekend.
There was no going back because a number of days had pasted.
Doing the above DTS method, there is no loss in data.
CHECKDB found 1 allocation errors and 957 consistency errors in table 'sysindexes' (object ID 2).
Any ideas on how to fixed this sysindexes table.
I've run dbcc updateusage, dbbc reindex on all tables, dbbc checkdb
Considering it is sysindexes, my guess you are in for a restore. If that isn't convenient, opening a case with
MS is probably a good idea (but chances are that they don't have better options either). General
recommendations for corrupt or suspect databases: http://www.karaszi.com/sqlserver/inf...suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Stephen" <stephen.hoye@.tabq.com.au> wrote in message
news:89575553-91E2-459B-B6CD-0709E5C79463@.microsoft.com...
> After running the command dbcc checkdb, which is part of a weekly job the following returned
> CHECKDB found 1 allocation errors and 957 consistency errors in table 'sysindexes' (object ID 2).
> Any ideas on how to fixed this sysindexes table.
> I've run dbcc updateusage, dbbc reindex on all tables, dbbc checkdb
>
|||I'm going to create a DTS package and move the database over to anthor DB.
Then I'l rename them. We do have back up, but the problem was picked up after I long weekend.
There was no going back because a number of days had pasted.
Doing the above DTS method, there is no loss in data.
Corrupted sysindexes
After running the command dbcc checkdb, which is part of a weekly job the following returne
CHECKDB found 1 allocation errors and 957 consistency errors in table 'sysindexes' (object ID 2)
Any ideas on how to fixed this sysindexes table.
I've run dbcc updateusage, dbbc reindex on all tables, dbbc checkdConsidering it is sysindexes, my guess you are in for a restore. If that isn't convenient, opening a case with
MS is probably a good idea (but chances are that they don't have better options either). General
recommendations for corrupt or suspect databases: http://www.karaszi.com/sqlserver/info_corrupt_suspect_db.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Stephen" <stephen.hoye@.tabq.com.au> wrote in message
news:89575553-91E2-459B-B6CD-0709E5C79463@.microsoft.com...
> After running the command dbcc checkdb, which is part of a weekly job the following returned
> CHECKDB found 1 allocation errors and 957 consistency errors in table 'sysindexes' (object ID 2).
> Any ideas on how to fixed this sysindexes table.
> I've run dbcc updateusage, dbbc reindex on all tables, dbbc checkdb
>|||I'm going to create a DTS package and move the database over to anthor DB
Then I'l rename them. We do have back up, but the problem was picked up after I long weekend
There was no going back because a number of days had pasted
Doing the above DTS method, there is no loss in data.
CHECKDB found 1 allocation errors and 957 consistency errors in table 'sysindexes' (object ID 2)
Any ideas on how to fixed this sysindexes table.
I've run dbcc updateusage, dbbc reindex on all tables, dbbc checkdConsidering it is sysindexes, my guess you are in for a restore. If that isn't convenient, opening a case with
MS is probably a good idea (but chances are that they don't have better options either). General
recommendations for corrupt or suspect databases: http://www.karaszi.com/sqlserver/info_corrupt_suspect_db.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Stephen" <stephen.hoye@.tabq.com.au> wrote in message
news:89575553-91E2-459B-B6CD-0709E5C79463@.microsoft.com...
> After running the command dbcc checkdb, which is part of a weekly job the following returned
> CHECKDB found 1 allocation errors and 957 consistency errors in table 'sysindexes' (object ID 2).
> Any ideas on how to fixed this sysindexes table.
> I've run dbcc updateusage, dbbc reindex on all tables, dbbc checkdb
>|||I'm going to create a DTS package and move the database over to anthor DB
Then I'l rename them. We do have back up, but the problem was picked up after I long weekend
There was no going back because a number of days had pasted
Doing the above DTS method, there is no loss in data.
Subscribe to:
Posts (Atom)