|
|
||||||
|
#1
09-30-05, 10:46 PM
|
|
|
|
|
We have SQL 2000 Enterprise Edition running on Windows 2000 Server. I ran
the DBCC Shrinkdatabase command last week. Now, the database is slow when I open one of the work orders. Do you have any recommendation on how to fix the slowness? Am I doing something incorrectly? I ran the following commands under Query Analyzer. Thank you. BACKUP LOG Support_DATA WITH TRUNCATE_ONLY GO DBCC SHRINKDATABASE (Support_DATA, TRUNCATEONLY) |
|
|
|
#2
09-30-05, 11:04 PM
|
|
|
|
|
Diane,
Just a guess...perhaps there is very little free space in the database and the growth interval is small (i.e., 1MB) so the database continually grows as new data is inserted. If this is the case, increase the size of the database and the the growth setting. Degrading performance can also be attributed to index fragmentation and out-of-date statistics. HTH Jerr "Diane Walker" <ett9300> wrote in message news:1132 [..] |
|
#3
09-30-05, 11:52 PM
|
|
|
|
|
The shrinkdatabase command isn't very useful in my opinion.
You don't have much control over which files are being shrunk to what size. Shrinking is typically something that you would do ad hoc and for a specific file using shrinkfile - after a run away transaction filled up the log, a database where the log wasn't being backed up and the size became too large, etc. The goal should be to size the files appropriately, do regular log back ups to keep the log size reasonable and avoid shrinking activities. The slowness may or may not be related to having shrunk the database last week. When you query the table, you would want to monitor what is going on - checking for other activity and locking/blocking by executing sp_who2 and querying the sysprocesses table in the master database. And you'd want to use something other than Enterprise Manager to view data in tables - especially if it has a lot of data. Enterprise Manager isn't necessarily a good tool to use for viewing or manipulating data. Use Query Analyzer instead. -Sue On Fri, 30 Sep 2005 14:46:53 -0700, "Diane Walker" <ett9300> wrote: [..] |
|
#4
10-01-05, 04:10 PM
|
|
|
|
|
Possibly autogrow as suggested or that indexes became fragmented due to the shrink:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp |
|
|
| Similar Threads | |
| Can I run the Dbcc Shrinkdatabase command on a company database We have a client who is near the 2 Gbyte MSDE limit but the database shows 400 mb unallocated. Can we run the shrink database command to buy them some time. They will need a... |
|
| DBCC SHRINKDATABASE Errors Running SQL Server 2000 , SP3a I am running SQL Server 2000 SP3a on Windows 2003 I get the following error when I run DBCC SHRINKDATABASE [Microsoft][ODBC SQL Server Driver][Shared... |
|
| Error running DBCC SHRINKDATABASE Msg 8966 When running DBCC SHRINKDATABASE on a SQL 2005 database the command returned the following error: Msg 8966, Level 16, State 2, Line 1 Unable to read and latch page... |
|
| DBCC Shrinkdatabase /shrinkfile not shrinking my database I have 137GB of database (mdf). it is showing on database properties that i still have about 63Gb available. If i go to EM-shrink file, i can have a minimum of 65GB which i... |
|
| RUNNING DBCC Shrinkdatabase Over the last 2 years, my database has grown to almost 12 gigs... I have been executing the code DBCC SHRINKDATABASE ([DBNAME]) inside a stored proc called by a SQL Job and... |
|
|
All times are GMT. The time now is 01:30 PM. | Privacy Policy
|
Database is running slow after running DBCC Shrinkdatabase command