Warning: SQL Admin is a newbie! :)
Setting: MFG Facility, 5 Stations adding records to
table 7 days a week, 24 hours a day.
I received a call that all stations were having a problem
adding records. The stations would scan a part which
would query the database and (based on a value) add the
part to the appropriate table.
Whenever they needed to add to the table, an hourglass
would appear and after a few minutes the record would be
added.
I went to the server (Windows 2000 Server, Dual
PIII933's, 144 Gigs of RAID 5 with 64 Meg Cache on the
controller, 3 Gigs of ram) and its utilization was below
3% and the database was at 2 gigs.
I decided to SHRINK the database and upon doing so,
everyone was able to work and response time was fine.
However, I must confess I am at a loss why running the
SHRINK command would have had such an impact. The DB
size nor the space free changed appreciably so I am not
sure why this would have helped so much...
Any feedback would be great as I am learning as much as I
can about SQL...
Larry Carnes
MCP/MCSE/MCT