November 11, 2008 at 12:21 am
pls. help me fro resolving this problem
ramesh
November 11, 2008 at 12:28 am
* use DBCC SHRINKFILE for more info see SQL BOL
* set the log file growth to restricted mode.
November 11, 2008 at 12:32 am
how repair sysindex table
November 11, 2008 at 12:41 am
Most chances are that your data recovery model is set to full, but you don't have any log backup. I reccomend that you'll read in Books On Line about data recovery model, so you'll be able to decide if you want to modify the recovery model or to schedule log backups. After you'll make this decision, you'll have to shrink the file using dbcc shrinkfile command (which you can read about in Books On Line as well).
Adi
--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
November 11, 2008 at 1:22 am
Please explain your problem in detail.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 11, 2008 at 1:30 am
Our Sql Server database log file size increasing huge and also not able to shirink database.
may be some problems with sysindex table becuse we ar trying to retrive data connect getting broken and an error is showing.
page(1:2506),slot 4 for text,ntext or image node does not exist
November 11, 2008 at 1:40 am
sramesh02 (11/11/2008)
Our Sql Server database log file size increasing huge and also not able to shirink database.may be some problems with sysindex table becuse we ar trying to retrive data connect getting broken and an error is showing.
page(1:2506),slot 4 for text,ntext or image node does not exist
run the following DBCC commands:
DBCC UPDATEUSAGE (0)
DBCC CHECKDB
DBCC DBREINDEX
DBCC DROPCLEANBUFFERS
DBCC FREEPROCCACHE
DBCC INDEXDEFRAG
DBCC SHRINKDATABASE
for more info see the SQL BOL.
November 11, 2008 at 1:48 am
Kishore.P (11/11/2008)
run the following DBCC commands:DBCC DBREINDEX
Only if you have several hours of downtime
DBCC DROPCLEANBUFFERS
DBCC FREEPROCCACHE
Not on a production server unless you want IO and CPU load to sharply increase. That wipes all of the cached data and plans out of memory
DBCC INDEXDEFRAG
Same comment as reindex, and is redundent with reindex
DBCC SHRINKDATABASE
No! Especially after rebuilding indexes. That badly fragments indexes. If the log file is large, then the log file alone should be shrunk, after figuring out why it's large.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 11, 2008 at 1:55 am
sramesh02 (11/11/2008)
Our Sql Server database log file size increasing huge and also not able to shirink database.
What recovery model is the DB in? How often are you doing log backups?
may be some problems with sysindex table becuse we ar trying to retrive data connect getting broken and an error is showing.
page(1:2506),slot 4 for text,ntext or image node does not exist
Please run the following and post the results. It may take a while to run, especially if your DB is big.
DBCC CheckDB (< Database Name > ) WITH NO_INFOMSGS
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply