I would not 'kill' things indiscriminately ... For example if your database recovery mode is 'full', the competing proces may have been a transaction log dump. The competing process could have...

Be careful in presenting your statistics. 'using the most' needs to be quantified first !

Based on what 'using the most' means can vary what profiler/perfmon information you gather, not to...

This behavior sounds like a'bug' to me. model databse size is used when no size is specified. I'll have to try this one out on my servers and see what...

Local hosts file entries and using IP addresses defeats the purpose of 'Name resolution' (not to mention that they can make for maintenance nightmares or better yet, hidden 'time bombs')...

If you remove money from the picture: System executables for SQL and master/model/msdb on internal server disk. Since you are using a 'service provder' I'd assume that they'd be using...

Just how large is 'large' ? 20 Gb, 50 Gb, 100 Gb ? This can be a factor in choosing your disk solution. Also, what type of insertion volume are...

My virtue of it's architecture a SAN should outperform internal disk 99% of the time. The SAN manufacturers have the performance monitoring software that you need - probably your SAN...

I would make sure that you are on MDAC v2.8 on the Citrix and on the SQL Server.

Are you sure it is being 'detached' or just being 'closed'. If it is being 'closed' that's an easy database option fix. If it is really being 'detached' then the...

The 1.61 Gb seems somewhat normal even though it can use 2 Gb. My non /3Gb servers use 1.8 Gb with min/max server memory set to 2048 (2Gb.. Even with...

I think that jvarunok quite eloquently stated the change in the profession that I've chosen to call the 'command line' DBA de-evoultion into the 'GUI' DBA. I'll stay a dinosaur thank you ... take...

Just a couple of things ... First 13 million rows instead of 1.3 million rows warrants partitioning potentially. Second, a GUID as a primary key will give you uniqueness, however if...

Economies of scale, TCO, Enterprise Management and Enterprise Monitoring ... maybe a few searches of MS and the web for whitepapers may give you some additional upper echelon information insights...

Does the SQL work from a QA window ? Is your MDAC up to date ? Does the Backup (Maintenance Plan) have 'VERIFY' checked ? If it does try removing...

By the way Steve, I've been s MS/SQL DBA since v4.21, Sybase since v4.9.2, DB2 since v1.0 and Oracle since v8. So there's no bias in my suggestion.