Viewing 15 posts - 31 through 45 (of 137 total)
Agreed but every poster needs to evaluate the information provided and implement for their environment and company as appropriate.
IMHO, someone else might see this post in the future and use...
May 18, 2009 at 10:15 am
I have to agree with Krishna's points.
Looking at your transaction log backup schedule and recovery model should be your starting point.
David
May 18, 2009 at 7:12 am
How frequently are you running log backups? The transaction being long enough so as to require the tlogto grow just doesn't sound right. Trans that long should...
May 16, 2009 at 8:54 pm
The select * into method will only create the table structure not any indexes or primary keys. Tables without indexes are going to slow. That is the first...
May 13, 2009 at 4:21 pm
Are you running the two test back to back? The second run sounds like it is benefiting from all the data being in the buffer pool (aka...
April 26, 2009 at 9:52 pm
Thanks for everyone's ideas and input. For my purpose I'm going to call this thread closed.
Take care,
David
April 22, 2009 at 12:09 pm
Rudy
I appreciate the direction you are taking this but this server configuration is rock solid. The server is not experiencing any obvious signs of a memory bottleneck. ...
April 21, 2009 at 6:53 pm
Jeff
I stand corrected on the clustered index point but the space used by the fragmentation versus the data deleted shouldn't be that significant?
David
April 21, 2009 at 2:55 pm
Hmmm, I must have mis-interpeted this post. Space isn't allocated to tables in Sql Server it is allocated to the database. If you deleted 8000 objects...
April 21, 2009 at 1:01 pm
USE master
go
DBCC SHRINKDATABASE('your_database_name_here', NOTRUNCATE)
go
DBCC SHRINKDATABASE('your_database_name_here', TRUNCATEONLY)
go
This command will shrink the database and should be run off hours. As always when making a change to adatabase have a backup you...
April 21, 2009 at 10:19 am
32 bit and awe is enabled. The server configuration is solid, I'm confident of that.
April 19, 2009 at 8:07 pm
Win2003 Sp1, Sql 2000 8.00.2187 12 gig of Ram, With 10 gig set as the max, no min is set.
I strongly doubt the server is memory hungry. ...
April 19, 2009 at 5:34 pm
Run this line of Sql and post the results.
Use your_database_name_here
go
exec sp_spaceused
go
April 17, 2009 at 3:38 pm
Jack suggestion was implemented and is working.
Thanks
March 17, 2009 at 2:14 pm
Viewing 15 posts - 31 through 45 (of 137 total)